"Nodes and Clients" page has outdated / missing information on clients' supported networks

[ThreeMuskets12]

Describe the bug

On the "Nodes and Clients" page, the 'networks' column of the execution clients section does not list Sepolia as a supported network for any clients.

Additionally, the 'networks' column of the consensus clients section does not list Sepolia's beacon chain or Ropsten's beacon chain as a supported network for any clients.

Also I feel like the way the 'networks' column of the consensus clients uses the beacon chain names for testnets instead of the execution chains for testnets is kind of confusing to end users, especially for networks that have already undergone The Merge. For example, it was discussed on Consensus Layer Call 91 that referring to the now-merged "Goerli + Prater" network should just be referred to as "Goerli". Source

To Reproduce
Steps to reproduce the behavior:

1. Go to '"Nodes and Clients" page'
2. Scroll down to the table under 'EXECUTION CLIENTS (FORMERLY 'ETH1 CLIENTS')'
3. See outdated / missing information in the 'Networks' column

Also

1. Go to '"Nodes and Clients" page'
2. Scroll down to the table under 'CONSENSUS CLIENTS (FORMERLY 'ETH2 CLIENTS')'
3. See outdated / missing information in the 'Networks' column

Expected behavior

-Sepolia should be listed as a supported network for all execution clients that support it
-Sepolia and Ropsten should be listed as supported networks for all consensus clients that support it
-[Potentially] network names for consensus clients should not be the name of the networks' beacon chain, and should instead be the name of the network itself. (IE not 'Prater' but 'Goerli')

Desktop (please complete the following information):

• OS: All
• Browser: All
• Version: All

[github-actions]

This issue is stale because it has been open 45 days with no activity.

[github-actions]

This issue is stale because it has been open 45 days with no activity.

[corwintines]

Closing with the above PR's merged in