Refactor whats_new with new ReleaseHighlight model

What does this MR do?

Moving logic from helpers and controller into a "model". The model doesn't have an associated table, and it's data is instead loaded from YAML.

Eventually I see us moving away from YAML and adding migrations to load from the DB instead.

This commit also adds filtering and a presenter, to return items that are platform specific.

part of: gitlab-org/growth/engineering#5388 (closed) #260363 (closed)

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team