Rename "Compliance" to "Conformance"

[DaveTryon]

We've been asked to use the term "Conformance" instead of "Compliance", "ComplianceStandard", or "Compliance Standard" in our code and docs. Since this would be a breaking change, we want to squeeze it into the 4.x release.

After this change, the terms "compliance" has 0 case-insensitive matches in the code base.

[DaveTryon]

/azp run

[DaveTryon]

/azp run

[github-actions]

This PR changes files in the API project. Does it change any of the API interfaces in any way? Please note that this includes the following types of changes:

• Changing the signature of an existing interface method
• Adding a new method to an existing interface
• Adding a required data member to a class that an existing interface method consumes

Because any of these changes can potentially break a downstream consumer with customized interface implementations, these changes need to be treated as breaking changes. Please do one of the following:

Option 1 - Publish this as a breaking change

1. Update the documentation to show the new functionality
2. Bump the major version in the next release
3. Be sure to highlight the breaking changes in the release notes

Option 2 - Refactor the changes to be non-breaking

1. Review this commit, which adds a new interface in a backward-compatible way
2. Refactor the change to follow this pattern so that existing interfaces are left completely intact
3. Bump the minor version in the next release

[DaveTryon]

/azp run