xfs: refactor log recovery resource capture

During regular operation, transactions are allowed to hold up to two
inodes and two buffers across a transaction roll to finish deferred log
items.  This implies that log recovery of a log intent item ought to be
able to do the same.  However, current log recovery code open-codes
saving only a single inode, because that was all that was required.

With atomic extent swapping and logged extended attributes upon us, it
has become evident that we need to use the same runtime mechanisms
during recovery.  Refactor the deferred ops code to use the same
resource capture mechanisms for both.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEUzaAxoMeQq6m2jMV+H93GTRKtOsFAmFzTREACgkQ+H93GTRK
tOucjA//Yf1Fityhc4gM+P0/20yAeDgTvp0sZtsSyGFNcFoxUN6jV+PDLg5VrqMR
C+ws36lKkPOItwXkbAke66FmUupV92XS8YUMVYk4h7s/G7Arh4U2yoSHBLynLTHw
73k5MRc7n9atuZRMD4peRrJ3WMuYFkh/o5YgVtLA0RTXXuuFrYs4b2TdbH2hkGPa
HsYOlGJhalAtLVPzd5bAqoikftiXWXyxMrBdquAccGZ7t0p6Dbzcnh8vKfvE+4eB
RW6VoV1imjrFYMYGqJ0kQNjbdP8MI/cF2O6hvt2dme73MxXkUlKK5p++p2U1iLvz
gH08DZFJue3nb3Rm7jYuENMCAGhhzj0/lh17xrUYJ/LU48RMVgatIgGRUfwVqIpe
W8tfqpk2KNC1zKR5JkPkf06ECpRc0AS2QOXegUharGE3cHNpPRdRw77nTx2/LOaP
tY6B1XCcGLNUbTZzPQRXL7Bki5j0LVP6gaqVKCzlVqlZizsriwrU6UJJfouSeFDy
x7NvV7zvbQEoSC/+i9g5TEq2Rm2ViuzER2+/LxFRDDiktIP6gJHbflAiwLY9wAEp
YdlISkn0PTkUSUojfjTL27uVxjlA8OyEphRqxZ+Q8LgPkAh3E4GWyFEEWJB2PmMa
cJGIoY8HkXQiBSlADq4CbEaLADI+0PfpT6khX3eMt24q2qjEUvo=
=/GSR
-----END PGP SIGNATURE-----