Refactor jobqueue to require initialized progress consumer

[peterargue]

The existing logic requires an storage.ConsumerProgressInitializer and a default value, then calls Initialize() in the constructor. This means that all data must be available at construction. Since the data is already available, let's do the initialization within the bootstrap, and pass in the completed object. I find this to be a more logical flow, and allows access to the ConsumerProgress earlier in the process so it can be queried to initialize other state within the components.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 9.47368% with 86 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
cmd/access/node_builder/access_node_builder.go	0.00%	35 Missing ⚠️
cmd/observer/node_builder/observer_builder.go	0.00%	21 Missing ⚠️
cmd/verification_builder.go	0.00%	21 Missing ⚠️
engine/testutil/nodes.go	0.00%	8 Missing ⚠️
...ne/verification/assigner/blockconsumer/consumer.go	75.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[peterargue]

close in favor of #8404