[Dynamic Protocol State] Architecture refactoring of dynamic protocol state

[durkmurder]

Context

After iterative changes to the implementation and addition of new features(KV store) we have observed that our architecture needs some changes in order to increase modularity, separation of concepts and better design in general. Proposed changes are summarized in next comments:

• https://github.com/onflow/flow-go/pull/5513#discussion_r1529468350
• https://github.com/onflow/flow-go/pull/5513#discussion_r1529510443
• https://github.com/onflow/flow-go/pull/5513#discussion_r1529191961
• https://github.com/onflow/flow-go/pull/5513#discussion_r1529560981
• https://github.com/onflow/flow-go/pull/5513#discussion_r1529650910

I would strongly suggest that we perform refactoring after integrating KV store with state mutator since we will have more understanding how the final architecture will look like when taking to account needs of KV store.