"Requires code in //chrome" showing in I2P template

[kyerebo]

Describe the bug
In the I2P template generated by CPS for posting to blink-dev, there is a section called "Requires code in //chrome". This seems like a bug in template generation as I don't see any corresponding fields in the CPS entry itself.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Start prototyping' in a Chrome Status feature entry.
2. Click on 'API Owners' pill.
3. Click on 'Draft Intent to Prototype email'
4. Observe that the generated template has a "Requires code in //chrome" section, that doesn't show up in any of the other fields of the Chrome Status feature entry.

Expected behavior
Either a corresponding field in the feature entry or doesn't show up in the template.

[GagandeepSingh20]

Hi, I’d like to work on this.

I found that the "Requires code in //chrome?" section is rendered in templates/blink/intent_to_implement.html based only on feature.feature_type_int != 2, so it can also appear for intent_type == 'prototype'.

My plan is to update the condition so this section is not rendered for I2P / prototype intents, and add or update a rendering test to cover this regression.

Please let me know if you’d prefer the alternative approach of adding a corresponding CPS field instead.