wip: Don't let user provide min_balance or is_sufficient as parameters to update_asset_metadata

[Garandor]

Description

Alternative 2 (see #1059) - prevent changing these

---

Before we can approve this PR for merge, please make sure that all the following items have been checked off:

• Connected to an issue with discussion and accepted design using zenhub "Connect issue" button below
• Added one label out of the L- group to this PR
• Added one or more labels from the A- and C- groups to this PR
• Explicitly labelled A-calamari, A-dolphin and/or A-manta if your changes are meant for/impact either of these (CI depends on it)
• Re-reviewed Files changed in the Github PR explorer.

Situational Notes:

• If adding functionality, write unit tests!
• 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]

All tests are passing but I'm 90% sure it's not safe to skip this insert. The Assets metadata got updated above and it never seems to be used from here (not sure why we store the AssetStorageMetadata anyway since we never do anything with it outside of Assets code) but frontend code might depend on asset_id_metadata returning the correct values somewhere

The interface has no mutators unfortunately, so not sure how to update the field otherwise

[github-actions]

⚠️ Congestion test: 1-day congestion cost (calamari) is NOT above target_daily_congestion_cost_kma