ci: Don't define `workflow:rules` for gems

What does this MR do and why?

Follow-up of !127794 (merged).

To reduce the risks of breaking the gems' child pipelines in the future, we shouldn't define workflow:rules for these as the parent pipeline is responsible for deciding when to run them.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.