Update MEV-relay-list.md

[sambacha]

The 'major incident' was a hack, which by the way revealed two underlying bugs with the flashbots relay. We were paid the only bounty flashbots has paid out ever in disclosing and fixing this bug as well.

Additionally, there have been other outages at Flashbots, Bloxroute, etc. It does not seem fair to only include our outage, which was a total of 7 ETH whereas Flashbots had over $20mil in their incident last May.

I added more information about running your own validator successfully and made note of a new Relay we are launching on mainnet this coming April (its on Holesky). as well as updated our holesky relay.

[remyroy]

We want to preserve and document all historic incidents regarding MEV relays. We are happy to add more incidents and references to pertinent documents about them.

Various clients are implementing boost configurations. It would be nice to describe it in details for each client.

I'm not sure about the need to add a seperate section for MEV Auction since it's the same endpoint as the regular one for Holesky.

If you want to rework this PR, I would be happy to include the rest.

[sambacha]

We want to preserve and document all historic incidents regarding MEV relays. We are happy to add more incidents and references to pertinent documents about them.

Various clients are implementing boost configurations. It would be nice to describe it in details for each client.

I'm not sure about the need to add a seperate section for MEV Auction since it's the same same endpoint as the regular one for Holesky.

If you want to rework this PR, I would be happy to include the rest.

Please suggest some criteria for the incident details needed

[remyroy]

I think a link to the post-mortem, a link to a summary or a link to any objective analysis of the incident would be enough in most cases.

[remyroy]

Continued in #123