Add a --create-object-mappings node CLI option

[teor2345]

This PR adds a --create-object-mappings CLI option to the node, which enables mapping generation for new and historic blocks. This option is implied by dev mode.

It also fixes the implementation of this feature to:

• correctly skip mappings in the first (partial) block passed to the archiver when it is initialised
• skip getting the runtime mappings, rather than skipping sending the notifications of those mappings

Code contributor checklist:

• I have read, understood and followed contributing guide

[teor2345]

I think this is what we want, but maybe the code is too strict on skipping some mappings?

[nazar-pc]

Make sense overall, but I'd call it --create-object-mappings instead of --force-mapping. And accordingly skip creation altogether if it is false (the default).

Those who need them would have to specify a CLI option, while everyone else would not have to pay the cost of runtime API calls and save some CPU cycles.