Differentiate between Consensus and Cluster Headers storage

[tim-barry]

A ChainID must now be provided to Headers storage instance on creation.
That storage instance will then only be able to successfully store or retrieve headers corresponding to the correct ChainID. In addition, the height-based index will also be specific to that ChainID.

Currently, an exception is made for cluster chains: Since the ChainID changes when a new epoch begins, but collection nodes still access collections from the previous epoch/chain (to deduplicate transactions), storage instances for cluster chains are allowed to retrieve (but not store) headers from other cluster chains.
This should likely be further refactored.

Closes: #4204

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[codecov-commenter]

Codecov Report

❌ Patch coverage is 9.31373% with 185 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...llection/epochmgr/mock/epoch_components_factory.go	0.00%	20 Missing ⚠️
state/protocol/badger/state.go	0.00%	20 Missing ⚠️
cmd/scaffold.go	0.00%	16 Missing ⚠️
storage/store/headers.go	31.25%	7 Missing and 4 partials ⚠️
state/protocol/util/testing.go	0.00%	9 Missing ⚠️
...ine/collection/epochmgr/factories/cluster_state.go	0.00%	8 Missing ⚠️
...ck-executed-height/cmd/rollback_executed_height.go	0.00%	5 Missing ⚠️
cmd/util/cmd/verify-evm-offchain-replay/verify.go	0.00%	5 Missing ⚠️
...d/util/cmd/exec-data-json-export/block_exporter.go	0.00%	4 Missing ⚠️
...d/exec-data-json-export/delta_snapshot_exporter.go	0.00%	4 Missing ⚠️
... and 26 more

📢 Thoughts on this report? Let us know!