Reimplement TransactAsset with FungibleLedger and AssetConfig traits

[ghzlatarev]

Description

closes: #534

• Replace FungiblesTransactor and LocalAssetTransactor tuple with our own AssetTransactor implementor called MultiAssetAdapter
• MultiAssetAdapter uses the unified interface of FungibleLedger trait to implement only the withdraw_asset and deposit_asset functions from TransactAsset
• The rest of the TransactAsset interface like can_check_in, teleport, etc are not required. Even though they were implemented in our old configuration they were not used.
• An additional burn function and implementation had to be added to our FungiblesLedger trait. This implementation allows accounts to go down to 0, as that was the behavior of the old configuration.
• ReducedToZero return results in can_withdraw implementation were considered an error, when in fact they are a success case, so switched that.
• XCM tests were refactored to account for the new configuration
• Refactored 1 manta-pay test which was supposed to fail because of attempting to mint more private assets than the available public assets of an account, but was actually minting the exact available amount. However since ReducedToZero was considered an error, this case was also holding up.

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
• Wrote unit tests.
• Updated relevant documentation in the code.
• Added one line describing your change in <branch>/CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer.
• If runtime changes, need to update the version numbers properly:
  • authoring_version: The version of the authorship interface. An authoring node will not attempt to author blocks unless this is equal to its native runtime.
  • spec_version: The version of the runtime specification. A full node will not attempt to use its native runtime in substitute for the on-chain Wasm runtime unless all of spec_name, spec_version, and authoring_version are the same between Wasm and native.
  • impl_version: The version of the implementation of the specification. Nodes are free to ignore this; it serves only as an indication that the code is different; as long as the other two versions are the same then while the actual code may be different, it is nonetheless required to do the same thing. Non-consensus-breaking optimizations are about the only changes that could be made which would result in only the impl_version changing.
  • transaction_version: The version of the extrinsics interface. This number must be updated in the following circumstances: extrinsic parameters (number, order, or types) have been changed; extrinsics or pallets have been removed; or the pallet order in the construct_runtime! macro or extrinsic order in a pallet has been changed. You can run the metadata_diff.yml workflow for help. If this number is updated, then the spec_version must also be updated
• Verify benchmarks & weights have been updated for any modified runtime logics
• If importing a new pallet, choose a proper module index for it, and allow it in BaseFilter. Ensure every extrinsic works from front-end. If there's corresponding tool, ensure both work for each other.
• If needed, update our Javascript/Typescript APIs. These APIs are officially used by exchanges or community developers.
• If modifying existing runtime storage items, make sure to implement storage migrations for the runtime and test them with try-runtime. This includes migrations inherited from upstream changes, and you can search the diffs for modifications of #[pallet::storage] items to check for any.

[Garandor]

merge conflicts to resolve

[Garandor]

LGTM, as it's an XCM PR I'd like to ask @Dengjianping and @stechu to review for approval here as well

[Dengjianping]

Please resolve clippy warnings.

[Dengjianping]

lgtm!
Great PR!

[Garandor]

Forgot i never sent this review 🥇

[Dengjianping]

lgtm!

[Garandor]

LGTM if you fix the changelog in #614 after merging this