Remove enable_in_development Key from Appeals Feature Flags

[kristen-brown]

Summary

After updating the values of a handful of Appeals feature flags in the development environment and then seeing the values change the next day, we eventually learned that the presence of enable_in_development: true in the feature flag config for these flags was overwriting the changes we had made to them in development.

Since we would like our changes to feature flags in dev to "stick," this PR removes enable_in_development: true from all Appeals (decision_reviews) feature flags.

Testing done

Was not able to test this change, but we expect the changes to these feature flags in the development environment to "stick" after this change is merged.

Screenshots

None

What areas of the site does it impact?

This PR impacts the decision_reviews feature flags in the development environment.

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable). – N/A
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution – N/A
• Documentation has been updated (link to documentation) – N/A
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog or Grafana (if applicable) – N/A
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected – N/A
• I added a screenshot of the developed feature – N/A

Requested Feedback

No specific feedback requested.

[caseywilliams]

Wow, I had no idea!