Two issues: 1316 (resolve to custom URL) and API 986 (feature flag clean-up)

[BradHN1]

Summary / Highlights

This PR addresses two issues: API 996 - removing some feature flags for approved features for all communities

1316 resolve to custom URLs for community sites which have them.

Details (Give details about what this PR accomplishes, include any screenshots etc.)

The main effect of this is for the custom URL sites. If you enter a page not using a custom URL, for example: https://community.massenergize.org/wayland/events the URL bar will resolve to: https://energizewayland.org/events

Testing Steps (Provide details on how your changes can be tested)

This should be tested on different browsers (Chrome, Safari, and others) and on mobile and laptop.

Requirements

• [x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• [x] I've tested my changes manually.
• [ ] I've added unit tests to my PR.

Transparency (Project board)

• [x] I've given my PR a meaningful title.
• [x] I linked this PR to the relevant issue.
• [x] I moved the linked issue from the "Sprint backlog" to "In progress" when I started this.
• [x] I moved the linked issue to "QA Verification" now that it is ready to merge.

What kind of change does this PR introduce? (check at least one)

• [ ] Bugfix
• [x] Feature
• [ ] Performance improvement
• [ ] Feature removal
• [ ] Code style update
• [ ] Refactor
• [ ] Docs
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [ ] Yes
• [x] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• [x] It's submitted to the dev branch or to a feature branch, not the main branch
• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• [ ] All tests are passing:
• [ ] New/updated tests are included

Other information: Any otherthing we need to know