Add FV test for host endpoint policy using a label inherited from a profile

[nelljerram]

Based on a failure in our OpenStack ST, I suspected that this scenario had stopped working, and so wrote this test to investigate. In fact the test passes, but it's worth keeping. There must be another explanation for the failure in the OpenStack ST.

Update: the OpenStack ST failure was caused by configuring a Profile with an invalid name, "test_profile". Underscore is not allowed as a character in Calico resource names. This used not to matter, but started mattering because of the change (also by me) to stream v3 Profile objects from the Felix syncer instead of the model/v1 ProfileLabels, ProfileRules and ProfileTags objects.

Release Note

None

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

• docs-pr-required: This change requires a change to the documentation that has not been completed yet.
• docs-completed: This change has all necessary documentation completed.
• docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

• release-note-required: This PR has user-facing changes. Most PRs should have this label.
• release-note-not-required: This PR has no user-facing changes.

Other optional labels:

• cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
• needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.