Add inter-boundary-component-direction-incoming-has-ipv-uri constraint (#930)

[DimitriZhurkin]

Committer Notes

This constraint tests the following scenario:
If direction is incoming, there must be at least one local ipv4 address, ipv6 address, or a URI to an API.

Related issue #930.

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Have you added an explanation of what your changes do and why you'd like us to include them?
• If applicable, have all FedRAMP Documents Related to OSCAL Adoption affected by the changes in this issue have been updated.?
• If applicable, does this PR reference the issue it addresses and explain how it addresses the issue?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

[Gabeblis]

Nice work!