Investigate and replace `xc-asset-config` pallet with orml `asset-registry`

[ashutoshvarma]

Explore if asset-registry pallet from orml can replace our xc-asset-config pallet. The orml pallet is preferred due to it's wider usage across ecosystem and will reduce our maintenance burden

What to do?

• Investigate asset-registry pallet, how it's used in other parachain and it's viability for replacing xc-asset-config pallet
• Replace xc-asset-config with it (need storage migration to remove pallet and keys) if effort makes sense
  (in case too much work is needed, we can omit it)

[ashutoshvarma]

Not required, current pallet works just fine but just awkward to use as designed to only contains latest xcm storage types (V5 rn).
It is breaking change and will require coordination

[Dinonard]

I see, makes sense.

It is breaking change and will require coordination

Given we get very little, or nothing by this, I hope we can avoid this change then.

designed to only contains latest xcm storage types

I don't remember the exact reason why I did it like that, but there was some problem back then with storing VersionedLocation into storage. We can revisit that if it helps.

However, can this migration be avoided?
Eventually old XCM versions will be deprecated, impacting the Versioned enum as well.