VM Rendered Config Context does not consider directly related site

[ChrisPortman]

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.8

Steps to Reproduce

1. Create a site
2. Create a Config Context and apply it to new site (step 1)
3. Create a VM and set its site to the one created above
4. DO NOT assign the VM to a cluster
5. Inspect the rendered context in the UI. Note that the site config shows as a source context but it is not merged into the rendered context.
6. Create a VM Cluster and assign its site to that created in step 1.
7. Update the VM to be a member of that cluster
8. Note that the rendered context for the VM now includes the sites config context

Expected Behavior

The VMs config context should include the sites context when it is directly related via the VM's site attribute with out requiring the cluster.

Observed Behavior

The VM context does not include the site context when it is directly related and not accessible via a cluster

[ChrisPortman]

I have a PR ready to resolve this

[jeremystretch]

1. Create a site with some config context

Sites do not have config context. Please elaborate on exactly what actions you're taking and what data you're providing at each step, so that someone else can confidently attempt to reproduce the bug.

[ChrisPortman]

@jeremystretch Sorry, you have to create the site, and then create the context and apply it to the site:

netbox/netbox/extras/models/configs.py

Line 63 in 1b9e6be

sites = models.ManyToManyField(