Regtest mainnet inscriptionId flag

[elocremarc]

@raphjaph I was thinking about the warning you added to PR 2357

ATTENTION: These ids will be different when inscribing on
mainnet or signet, so be sure to change those in your recursive inscription for
each chain.

Would it be possible to have ord use the mainnet inscriptionId when inscribing say a library to use in regtest? This is relatively easy to manage with say matterJs since it is a single file. I am doing this already with ord package manager tracking it in the regtest.json

However it becomes less trivial to manage regtest and mainnet inscriptionIds with say React. It has multiple levels of recursion.
For example a flag could look something like this:
ord -r wallet inscribe matter.js --fee-rate 1 --inscription-id 9d567e6ef8bd6b13458cc67cc5e8339395a4433e45db4554ff83c88a5df8bae2i0
This would make it so that the libraries and any dependencies they have can be tested as though they were on mainnet.

It would be even cooler if you could just take any inscriptionId that is in your mainnet index and do the same thing.
ord -r server --mainnet-inscrition-Id 9d567e6ef8bd6b13458cc67cc5e8339395a4433e45db4554ff83c88a5df8bae2i0
This would replicate what ever dependencies your gonna need from mainnet in your regtest setup.