(CONT-1229) - Allow nested extra networking facts

[jordanbreen28]

Summary

This change allows the user to specify nested facts within their .sync.yml.
Before, if a user specified a networking fact in their .sync.yml with the below

spec/default_facts.yml:
  extra_facts:
    networking:
      hostname: "kubernetes.localhost"

it would result in a duplicate key error in the default_facts.yml, like this:

networking:
  ip: "172.16.254.254"
  ip6: "FE80:0000:0000:0000:AAAA:AAAA:AAAA"
  mac: "AA:AA:AA:AA:AA:AA"
is_pe: false
networking:
  hostname: "kubernetes.localhost"

Additional Context

Now, when extra_facts is passed it will check for networking facts first, before clearing them and adding extra_facts as before.
A .sync.yml like below, will result in the following:

spec/default_facts.yml:
  extra_facts:
    networking:
      hostname: "kubernetes.localhost"
      domain: "localhost"
      fqdn: "foo.example.com"
    os:
      family: "debian"
      name: "debian"

default_facts.yml

---
networking:
  ip: "172.16.254.254"
  ip6: "FE80:0000:0000:0000:AAAA:AAAA:AAAA"
  mac: "AA:AA:AA:AA:AA:AA"
  hostname: "kubernetes.localhost"
  domain: "localhost"
  fqdn: "foo.example.com"
is_pe: false
os:
  family: debian
  name: debian

Related Issues (if any)

Mention any related issues or pull requests.

Checklist

• 🟢 Spec tests.
• 🟢 Acceptance tests.
• Manually verified.

[david22swan]

LGTM