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+H93GTRKtOsFAmFFRzkACgkQ+H93GTRK
tOtaSBAAqVpPMUJc+lJ3M5y7TA/PJh5UQ1NyiymwqT3hpmVp8UJF9XYZOTtffjde
IQ6XWY+XyATX8taUJYinH+e2tAR5DArRmMGPgaGz9Y90oW9IrFh8hugUeCkP1kZn
tnE74pQrsLH23u17W0m8BTobW1lzsPl46mAG/JF+RfiV6OJQjEQ3XSAm+S5furs0
GKwGpLpwCiY0XrDgdtQyjH7gUAi51jt+dnB1Usb/HEZ32ACDzmTEw/qQobhSzaod
9VIMzCIm0i3j+b7DrF5kdsY2DSRWfmZ9b4dNZqrycNaYQv+eclznPX2zCM2zntuL
t01OGNsqqEqSsxdXpyQgLiUIMJi9kDWM9s2CV8/ogt1b34QxTz4OdozjjZ/Jk3vl
ub3ZtUuusZvXQn0pZ7YUwB7Oe9MD/fmmfjBRa31rzGAUOH5yFP3/mV+/wEO5b4mm
lNa1SxnqqYNKbnC32MPucDhrHcPp5xFK7bs+nZKU32GZEkwsB8eL4s54LvEk72xd
tQJTb00Aux1tmiGL8Y8h2FKd/mxXr0KZf4VbpH2JN35Dw5hGrbQZkhWNVE33cKsi
C8RjcqJQIVy+agkHYYVC3eZQTEeF5IzWEng1+C6KcfqTRSBV+pfCsL1N9dIURuGW
bn4yyFPd+9X5t9nVskLDDvUMSXi9a9jizWwnP94lrF6zfOyBnVQ=
=9y9U
-----END PGP SIGNATURE-----