Trigger liboqs-java and liboqs-rust downstream CI

[SWilson4]

This PR adds triggers for liboqs-java and liboqs-rust to the trigger-downstream-basic workflow.

Marked as draft pending merge of downstream PRs open-quantum-safe/liboqs-rust#271 and open-quantum-safe/liboqs-java#30.

• Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)? (If so, a version bump will be required from x.y.z to x.(y+1).0.)
• Does this PR change the list of algorithms available -- either adding, removing, or renaming? Does this PR otherwise change an API? (If so, PRs in fully supported downstream projects dependent on these, i.e., oqs-provider will also need to be ready for review and merge by the time this is merged.)

[baentsch]

LGTM. But why is this in Draft only?

[SWilson4]

LGTM. But why is this in Draft only?

Until open-quantum-safe/liboqs-rust#271 lands, the repository_dispatch API call will fail, which would break liboqs CI on main if this PR were merged.