Main domain / subdomain CORS issues on Forge for Multi Tenancy

When working with Tenancy for Laravel and using the SaaS kit, you might encounter this problem on your Forge server:

Access to script at 'https://example.com/' (redirected from 'https://subdomain.example.com/tenancy/assets/build/assets/app.d06d9252.js') from origin 'https://subdomain.example.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

As of 20 November 2024 I don't have a solution for this problem. Tenancy for Laravel and subdomain based multi tenancy was a thing when I started my journey but I've defaulted to the scoped way as harnessed by Filament's multi-tenancy.