Rule sets not dragable for drag and drop

[ksstille]

Before submitting:

• I have searched existing issues to make sure this is not a duplicate.
• I am using the latest release.
• I agree to follow the Code of Conduct.

Bug description

Policy rule sets are not dragable for drag and drop which is needed to use a policy in a branch rule. Thereby it is not possible to branch to another policy rule set. Instead only the following lines are marked. Same dragging problem for NAT and Routing rule sets.

Steps to reproduce

Make a rule with a branch action and an additional policy rule set.
Try to drag the new policy rule set to the configuration of the branch action.

Expected behavior

Local policy should be added to branch rule.

Environment

Ubuntu 25.10
Python 3.14.3
firewallfabrik 1.4.6

Additional context

No response

[markuslf]

Surface bug for #90 (the Branch-action pipeline is only partially ported in fwf). Three layers are unwired: drag source (rule-sets blocked in NON_DRAGGABLE_TYPES), drop receiver (actions_dialog.BranchChainPage has no Python wiring, branch_id is never written), compiler (no resolution of branch_id).

The next rc removes the "Branch" entry from the Policy and NAT action context menus so users no longer create branch rules that won't compile. Issue stays open until the full branch pipeline lands.

[markuslf]

"Branch" action removed from Policy and NAT context menus in v1.5.0rc4. Issue stays open until #90 lands.

[markuslf]

Fixed on main.

Policy, NAT and Routing rule sets can be dragged in the object tree again, which is what the Branch action needs. The full path: right-click the Action cell of the rule → Branch, then drag the rule set from the tree onto the "Drop a rule set here" field that appears in the editor below. The target survives saving and reopening the file.

Dropping a rule set anywhere else is still refused, so it cannot land in a Source, Destination or Service column by accident.