Girazoki support both pre and post 0.9.16 anchoring logics for native token

[girazoki]

What does it do?

It adds support for mapping both pre and post 0.9.16 anchoring changes to the same token (in this case, the native token).

The reanchoring logic change will stop from marking us see our token as

MultiLocation {
  parents: 1,
  interior: X2(Parachain(para_id), PalletInstance(balances_pallet))
  }

To make it see it as

MultiLocation {
  parents: 0,
  interior: X1(PalletInstance(balances_pallet)
 }

This PR does yet not add the possibility of transferring the local token for Moonriver and Moonbeam. I wanted this review to be easier, so I will make a follow up PR enabling transfer of the local asset in XCM

What important points reviewers should know?

Is there something left for follow-up PRs?

Adding the possibility of transferring the local token for Moonriver and Moonbeam

What alternative implementations were considered?

Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?

What value does it bring to the blockchain users?

[girazoki]

Merged in #1274