chore(build-system-test): Run build system tests pre-release and on schedule

[esauerbo]

Description of changes

• Makes build system tests a reusable workflow that's invoked pre-release (publish-latest, publish-next, publish-hotfix) and on a cron job every hour for RN, and half hour for other frameworks (we're already doing this)
• Updates build system test scripts to accept a tagged version of an Amplify ui package (defaults to latest)

Issue #, if available

Description of how you validated changes

POC https://github.com/aws-amplify/amplify-ui/pull/5695 (workflows are the same except I removed publish and log steps)

Workflow runs: Verified they pass (except hotfix which points to a really old version) and made sure the correct tagged version was installed

Canaries

• Build system RN canary https://github.com/aws-amplify/amplify-ui/actions/runs/10601974345
• Build system canary https://github.com/aws-amplify/amplify-ui/actions/runs/10601974348 (didn't touch this workflow but included since I changed the mega-app scripts )

Pre-release

• Publish latest https://github.com/aws-amplify/amplify-ui/actions/runs/10601974353
• Publish next https://github.com/aws-amplify/amplify-ui/actions/runs/10601974355
• Publish hotfix https://github.com/aws-amplify/amplify-ui/actions/runs/10601974342 (fails on build step because hotfix is from a prev major version)

Checklist

• [ ] Have read the Pull Request Guidelines
• [ ] PR description included
• [ ] yarn test passes and tests are updated/added
• [ ] PR title and commit messages follow conventional commit syntax
• [ ] If this change should result in a version bump, changeset added (This can be done after creating the PR.) This does not apply to changes made to docs, e2e, examples, or other private packages.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.