Closes #20399: Add assigned and primary filters for MACAddress

[pheus]

Fixes: #20399

This PR introduces two boolean filters on MACAddress — assigned and primary — to improve filtering capabilities across the UI, REST, and GraphQL. It also adds an is_primary as a boolean column on the MAC Address table for quick visual scanning.

Summary of Changes

• FilterSet (REST/UI):
  • Add assigned (true ⇒ MACs bound to any Interface/VMInterface; false ⇒ unassigned).
  • Add primary (true ⇒ MACs set as the primary MAC on any Interface/VMInterface; false ⇒ all others).
• GraphQL:
  • Wire the above filters into the GraphQL filter class to maintain parity with REST/UI.
• UI / Tables:
  • Add is_primary as a boolean column on the MAC Address table.
• Forms:
  • Expose the new boolean filters in the MAC Address filter form.
• Tests:
  • Unit tests for both assigned and primary filters (true/false cases).

API Examples

REST

GET /api/dcim/mac-addresses/?assigned=true
GET /api/dcim/mac-addresses/?primary=false

GraphQL

query {
  mac_address_list(filters: { assigned: true, primary: true }) {
    id
    mac_address
  }
}

Backward Compatibility

• Additive change only; no existing behavior is altered.
• No database migrations.

Implementation Notes

• The table’s is_primary column is backed by a cached property to avoid repeated lookups while browsing tables.

---

Naming Notes

These filters are currently named assigned and primary to match existing boolean filter conventions. If the project prefers is_assigned / is_primary, I’m happy to adjust.

Happy to take any naming or scope adjustments the maintainers prefer. Thanks for the review!

[pheus]

Thanks for the review!
Quick note here: I imported VMInterface directly, while Interface is referenced via dcim.models (models.Interface). If you’d prefer consistent namespacing, I can switch to from virtualization import models as virtualization_models and use virtualization_models.VMInterface. Happy to adjust either way!

[arthanson]

Thanks @pheus !