Motivation and Rationale needs to be fleshed out

[adrianmcli]

The Motivation and Rationale sections currently only contain a couple of sentences each. These sections are crucial because they "sandwich" the Specification section, providing the necessary context and reasoning.

• The Motivation acts as the problem statement, helping everyone understand what we're trying to solve.
• The Rationale explains why the proposed spec is the right way to solve that problem.

To make this EIP as clear and compelling as possible, we need to flesh out these sections more thoroughly.

Here are some ways to flesh them out (according to ChatGPT):

Motivation Section:

1. Background: Briefly outline the issue's history or relevance.
2. Examples: Cite specific cases where the problem exists.
3. Impact: State who's affected by the issue.
4. Goals: List what the EIP aims to achieve.

Rationale Section:

1. Alternatives: Mention other solutions considered and why they're not chosen.
2. Tech Justification: Give technical reasons for the chosen solution.
3. Feedback: Summarize community input and its impact on the EIP.
4. Vision: Explain how the EIP fits into broader goals.

[adrianmcli]

I've assigned myself for now, but if anyone else has time, feel free to get started.

Also, I think we will be borrowing a lot from the blog post for these sections.