Prevent modification/deletion of rules belonging to a subscription

[dmjb]

Summary

Relates to #2543

These methods ensure that it's not possible to create/update/delete
bundle/namespaced profiles or rule types through the API.

Dedicated methods are supplied for creating these entities with a
subscription ID. These methods will be called by the bundle
management code which will be implemented in a follow up PR.

Patch and delete methods which have not yet been migrated to the
respective service interfaces have been modified to prevent modification
of bundle rule types/profiles.

Rules

1. Rules and profiles belonging to bundles must have namespaced names.
2. A namespaced name consists of two DNS-like IDs separated by a slash
3. Rules and profiles which were created from a bundle have a foreign key reference back to the subscription they were created from.
4. It is not possible to create a rule/profile with a namespaced name through the API.
5. It is not possible to update or delete a profile/rule with a reference to a subscription through the API.

Change Type

Mark the type of change your PR introduces:

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[coveralls]

coverage: 46.534% (+0.08%) from 46.455%
when pulling ad1338f on bundle-namespace-intf
into 7b9a05a on main.