VACMS-24082 Add branching logic and feature flag availability for new outreach material topics

[chriskim2311]

…terials topics

Description

What does this PR address?

Ticket

Closes link to ticket

Developer Task

- [ ] PR submitted against the `main` branch of `next-build`.
- [ ] Link to the issue that this PR addresses (if applicable).
- [ ] Define all changes in your PR and note any changes that could potentially be breaking changes.
- [ ] If you've changed a content type, star and add notes to the appropriate URL(s) in the [QA tool](http://localhost:3000/_playground/qa/) so reviewers can test your changes.
- [ ] PR includes steps to test your changes and links to these changes in the Tugboat preview (if applicable).
- [ ] Provided before and after screenshots of your changes (if applicable).
- [ ] Alerted the #next-build Slack channel to request a PR review.
- [ ] You understand that once approved, you are responsible for merging your changes into `main`. (Note that changes to `main` will move automatically into production.)

Testing Steps

Explain the steps needed for testing

QA steps

What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?

Screenshots

Before:
After:

Is this PR blocked by another PR?

• Add the DO NOT MERGE label
• Add links to additional PRs here:

---

Reviewer

Reviewing a PR

This section lists items that need to be checked or updated when making changes to this repository.

Standard Checks

- [ ] Code Quality: Readabilty, Naming Conventions, Consistency, Reusability
- [ ] Test Coverage: 80% coverage
- [ ] Functionality: Change functions as expected with no additional bugs
- [ ] QA: Changes are QA'd in the Tugboat preview or locally (use the [QA tool](http://localhost:3000/_playground/qa/) to test)
- [ ] Performance: Code does not introduce performance issues
- [ ] Documentation: Changes are documented in their respective README.md files
- [ ] Security: Packages have been approved in the TRM

Merging a Layout

When merging a layout, you must ensure that the content type has been turned on for next-build in the .tugboat.env. This method mocks the CMS flag that must be turned on for a layout to be included in the build.

The layout component and matching resource type should be included in the slug.tsx, so that it can reviewed. Including a component in the slug.tsx does not mean a page will be viewable in production only on the tugboat for the branch.

When a layout is merged to main and approved for deployment, the prod CMS will turn the toggle on for the resource type.

The status of layouts should be kept up to date inside templates.md. This includes QA progress, development progress, etc. A link should be provided for where testing can occur.

[va-cms-bot]

Tugboat has finished building the preview for this pull request!

Link:

• https://pr1855-opexlb2ns9mixjlbehflrnpiuifqb1mb.tugboat.vfs.va.gov

Link (redis):

• https://pr1855-fgrzicaxf80acio6rpeew1wppjub3d7t.tugboat.vfs.va.gov

Dashboard:

• https://tugboat.vfs.va.gov/69ea80ad343c501b6f185b05