feat: Add Rack Groups Nautobot Operator

[abhimanyu003]

Summary

This PR adds Rack Groups sync support to the Nautobot Operator.

The operator now reads Rack Groups defined in a Kubernetes ConfigMap and ensures they are created and kept in sync with Nautobot via the Nautobot API.

How it works

1. The Nautobot Operator reads the Location configuration from a Kubernetes ConfigMap.
2. It processes only the Location that are referenced by the Nautobot CRD.
3. The operator then syncs these Location with Nautobot using the Nautobot API.

flowchart
    n1["Nautobot Operator"]
    n2["Kubernetes Rack Groups ConfigMap"]
    n3["Nautobot API"]

    n1 --> n2
    n2 --> n3

Loading

Example ConfigMap

data:
  rackgroups.yaml: |
    - name: IAD3 STAGING ENV
      description: Staging environment fabric
      location: IAD3
      children:
        - name: IAD3 STAGING CHILD
          description: Staging environment fabric
          location: IAD3
metadata:
  name: rackgroups
  namespace: nautobot

Important

• This feature uses a new manifest structure based parent-child relationships.
• Location must be defined using the children field to represent the multiple children.

Example hierarchy:

Global
└── RackGroup
    └── ChildRackGroup

[skrobul]

Please cross check if all resources are named correctly too - i.e. LocationType vs Location in

[skrobul]

Also, please rebase to remove the CI failure for pyright