Intent to Prototype email contains fields for later stages

[davidben]

Describe the bug The generated I2P emails contain all this extra stuff:

TAG review None

TAG review status Pending

Risks

Interoperability and Compatibility None

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android > WebView-based applications?

None

Debuggability None

Is this feature fully tested by [web-platform-tests](https://chromium.googlesource.com/chromium/src/+/main/docs/testing/> web_platform_tests.md)? No

Flag name on chrome://flags None

Finch feature name None

Non-finch justification None

Requires code in //chrome? False

Estimated milestones No milestones specified

However, none of those fields are filled in at the "Start prototyping" stage of the website. This is extremely confusing.

To Reproduce Steps to reproduce the behavior:

1. Follow the instructions to launch a feature
2. Look at the generated email

Expected behavior The generated email is consistent with the instructions on the website, and doesn't contain fields that the website hasn't asked for yet.

Additional context Based on the instructions, the fields on the website seem to be correct. Most of these fields are far, far too early for just beginning to prototype. But, in that case, they should not be included in the generated email.

[dadrian]

While this bug is for I2P, this general failure mode applies to basically every single generated email by Chrome Status. Most of the fields that are filled in for generated emails at a step are not only not prompted for at that step, but are not prompted for anywhere. Getting them autofilled requires digging in "Edit All Fields" to find the corresponding underlying field, if it exists at all.