DAL/Proto: store Dal constants for each protocol

What

Generalise !19548 (merged) to store both all parameters, not just attestation lag (it's not yet strictly necessary to store everything), but also store these for each protocol, not only the previous one.

Why

Because for any protocol we want to know the DAL revealed parameters based on a Tezos level, it's not necessarily the current protocol nor the previous one.

How

It's almost the same logic as what was done for the changing commitment periods Sc_rollup_storage.

Manually testing the MR

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR