Feature: EL client version in the default graffiti

[one-three-three-seven]

Is your feature request related to a problem? Please describe.
Having no (super)majority client within the network is important for the network's fault tolerance. Unfortunately, determining the distribution of clients is not straightforward. My project, https://supermajority.info, aims to achieve this through surveys. However, it is not feasible to survey many smaller, unknown operators.

Describe the solution you'd like
Most other clients have begun including the execution layer client they use in the graffiti. See the following links:

ethereum/execution-apis#517
https://hackmd.io/@wmoBhF17RAOH2NZ5bNXJVg/BJX2c9gja
https://clientcode.supermajority.info/

The graffiti can be used as an additional data source to improve the existing data about client diversity.

Describe alternatives you've considered
Surveys are an alternative, but only a tiny fraction of operators respond to them.

Additional context
I am aware of the security and privacy concerns. However, Nimbus already publishes its own version in the default graffiti, such as Nimbus/v24.9.0-f54a03-stateofus. Therefore, mentioning the execution layer client would only marginally worsen the situation. In my opinion, it is somewhat inconsistent to publish the version of Nimbus but not that of the execution layer client.

Additionally, the information could be limited to the client name rather than specifying the exact version, for example, NMNB. This way, the exact version being used would not be disclosed.

If the decision is made to implement it, it would make sense to do so before Pectra. This is because the operators will have to update the clients anyway, allowing us to gather the data as soon as possible. Some operators tend to update the clients only when it is necessary.