Change : asset registry - dont enforce asset id in reserved range if registered from genesis config

It is possible to pre-register an asset by specifying them in the genesis config

However this enforces the provided ID to be in certain range.

This is not good if eg. we want to copy a mainnet state using genesis configs.

Suggestion how to implement: add a flag to do_register_asset to provide info if this is coming from genesis or not, and skip the check in that case.

Start at do_register_asset and trace the genesis-config call path to find where the reserved-range validation is applied. Verify that genesis registrations can use IDs outside the reserved range while non-genesis registrations retain the check, then update the relevant tests if they are present.

Written by the indexing model from the issue text.