Idea: Add L2 Configuration Fields

As more L2+s are launching, there are many more interesting and useful fields for analysts and chain consumers. A huge personal painpoint has been [trying to track](https://github.com/ethereum-optimism/op-analytics/blob/main/op_chains_tracking/inputs/chain_metadata_raw.csv): "How many chains are built using the OP Stack? How many are using L1 DA? etc."

Since these chains will get added to this list in some sort, I thought this would be a great spot to capture some of this information. [L2Beat](https://l2beat.com/scaling/summary) tracks most of this information today, but is not (yet) exhaustive of all chains.

Listing ideas below, but open to discussion about 1) Does this make sense?, 2) If so, what should these fields look like?

- **Rollup Software**: OP Stack, Arbitrum, zkSync Stack, Polygon SDK, etc
- **Prover Type**: Optimistic, ZK, etc
- **Data Availability Layer**: Ethereum, Celestia, EigenDA, BNB, Polygon PoS etc
- **State Output Layer**: Ethereum, Base, BNB, etc
- ?

Start by reviewing op_chains_tracking/inputs/chain_metadata_raw.csv and the existing chain metadata structure referenced in the issue. Clarify which fields and values should be supported before implementation; done means an agreed schema that captures the selected L2 configuration data for relevant chains.

Written by the indexing model from the issue text.