Support for configurable QoS in built-in bridge?

[jarhodes314]

Following the discussion in #3918 (comment), we need to determine if and how to support QoS != 1 in bridge rules. The current implementation defaults to 1 to match the existing built-in bridge behaviour.

If this is something we wish to implement, at the very least we need to answer the following questions:

1. Should QoS customization happen at the template level, the rule level, or both?
2. Do we configure QoS for local and cloud subscriptions separately, or assume they can just be the same?
3. Is 1 the correct default? (Likely yes, but worth confirming).