API: Feature Hypothesis and Prototype field length doesn't match the UI

Issue Summary

The fields Hypothesis and Prototype present on the Desing tab of Features allow the UI more chars than the API does. The Hypothesis seems to allow > 2k, while Prototype allows for 350 on the UI, but, for both, the API limit is 250.
So, if you fill these fields on the UI, do a GET and try a POST, it will fail the call.

Steps to Reproduce

1. Create a Feature, go to the Desing tab and fill both fields with 300chars or more
2. Do a GET API call for the Feature
3. Now using it as content, do a POST call to the same Feature
4. Or try a PATCH call with 300 char for these fields

Expected Results

To be defined by PM.

Actual Results

The length side of the fields on the UI x API doesn't match.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available