feat(resources): add redirect domain management in settings

[LaurenceJJones]

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

I’m not sure of the best migration approach here, since this feature requires adding a new column to the resources table so its bundle inside of the PR, but maintainers may want to change it to a minor version since its a new feature?

however, there may be another option which we create a dedicate table for this? 🤷🏻

• add redirect domains section in resource settings
• add "Add Redirect" flow using DomainPicker
• validate redirect domains to prevent primary-domain and duplicate entries
• normalize redirect domains before save (ASCII/lowercase)
• support removing redirect domains from the configured list
• add translation-key fallbacks for new redirect copy

How to test?

When editing a resource, under the general tab you now have "Redirect" options which allow you to set subdomains or another domain (that added in the system) to redirect to the currently edited resource. This is useful as users may host a website on the base domain and requests to www. should be redirected to the base domain on a permanent redirect (or the reverse depending on the user preference).

Before scaffolding this feature the only option would be to create another resource that take the subdomain and points to the same target, however, that is not scalable and creates duplicate records.

Open to comments/feedback on the PR as direction may have to change or may prompt new ideas on how to achieve this.

[LaurenceJJones]

Thinking more about the feature, it may be better design decision to think of these as "HTTPS" resources which could either point towards another resource so for example in the "target" section instead of a site + url it could just be an extension then there is more power in the resources section as nothing is hidden under the edit tab of a resource?