Authorize access by CIDR range

[willthames]

Allow access by CIDR range and optionally also by access group ID.

Types of changes

What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING.md doc.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

Further comments

[adenot]

Thanks for the PRs @willthames.

Just to inform that the README Inputs and Outputs sections are automatically generated with tfdocs (see Github Action). So no need to make changes in the README file as they will be overwritten by the action.