[CI Testing] Add manual GHA triggers for Drake PRs

[tyler-yankee]

This introduces parameters on each of the GitHub Actions examples to be able to run the CI jobs with alternative versions of Drake. Towards #22574.

Changes to each example are as follows:

• drake_cmake_installed: install an experimental package of Drake into $HOME/drake, and use that when cmake -DCMAKE_PREFIX_PATH=<path> .. is called to configure/generate
• drake_cmake_installed_apt: uses apt-get install <url> with a link to an experimental package
• drake_bazel_download: similar to drake_cmake_installed, but uses Bazel's --override-repository flag when calling bazel test //...
• drake_pip: uses pip install <url> with a link to experimental wheels (note: does this after installing drake from requirements.txt, in case any other packages are added to that file in the future)
• drake_poetry: similar to drake_pip, but uses poetry add <url>

Additionally, modifies the CI config files to add parameters to the workflow_dispatch event.

• linux_jammy_package_tar
• linux_jammy_package_deb
• mac_arm_sonoma_package_tar
• linux_jammy_wheel
• mac_arm_sonoma_wheel

The use case here is that a developer with a PR on Drake could test their changes on DEE with the following workflow:

• Run experimental packaging builds on Linux Jammy and macOS Sonoma and obtain the artifact URLs.
• Run experimental wheel builds on Linux Jammy and macOS Sonoma and obtain the artifact URLs.
• Navigate to DEE's Actions page and kick off a build of all GHA examples, inputting the URLs from above.

Tested via GHA on my forked repo (TODO will insert link here).

This change is