feat: add location type sync to nautobot operator

[abhimanyu003]

Summary

This PR adds Location Type sync support to the Nautobot Operator.

The operator now reads Location Types 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 Type configuration from a Kubernetes ConfigMap.
2. It processes only the Location Types that are referenced by the Nautobot CRD.
3. The operator then syncs these Location Types with Nautobot using the Nautobot API.

flowchart
    n1["Nautobot Operator"]
    n2["Kubernetes Location Type ConfigMap"]
    n3["Nautobot API"]

    n1 --> n2
    n2 --> n3

Loading

Example ConfigMap

apiVersion: v1
kind: ConfigMap
metadata:
  name: location-types
  namespace: nautobot
data:
  location-types.yaml: |
    ---
    - name: Global
      description: Global (Root)
      content_types: []
      nestable: false
      children:
        - name: Company
          description: Company
          content_types:
            - "ipam.namespace"
          nestable: false
          children:
            - name: Region
              description: Region
              content_types: []
              nestable: false
              children:
                - name: Site
                  description: Site
                  content_types:
                    - "dcim.device"
                    - "ipam.vlan"
                  nestable: false

Importan

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

Example hierarchy:

Global
└── Company
    └── Region
        └── Site

[skrobul]

overall LGTM, some minor copy&paste leftover

[skrobul]

+1, rebase pls