Added support for Static AAEPs via EPG - fvRsAepAtt

[manofcolombia]

Tested on apic: 6.1.3g

Here is a sample of the yaml for updating the nac json schema

endpoint_groups:
  - name: TEST_EPG
    static_aaeps:
      - aaep: TEST_AAEP (required)
        encap: 1500  (required)
        primary_encap: <int> (optional)
        mode: <default: regular> (optional)
        deployment_immediacy: <default: lazy> (optional)

[manofcolombia]

In this state, subsequent deployments of fvRsAepAtt objects will consistently come back with changed annotations due to annotation being utilized to indicate if the relationship to AAEP has been formed properly.

  # module.nac_aci.module.aci_endpoint_group["LU/NUTANIX_APP_PROF/AHVPROD_EPG"].aci_rest_managed.fvRsAepAtt["AHV_AAEP"] will be updated in-place
  ~ resource "aci_rest_managed" "fvRsAepAtt" {
      ~ annotation  = "FORMED" -> "orchestrator:terraform"
        id          = "uni/tn-LU/ap-NUTANIX_APP_PROF/epg-AHVPROD_EPG/rsaepAtt-AHV_AAEP"
        # (4 unchanged attributes hidden)
    }

I have not seen an annotation used to indicate the formation of a relationship before. Is this intended or a misuse of annotation? For now I have set annotation to be ignored.