Adding TLS options validation as final sig-network review follow up

[robscott]

What type of PR is this?
/kind cleanup
/kind api-change

What this PR does / why we need it:
I found a comment from @khenidak that I'd missed from the original sig-network review suggesting more thorough validation here. This adds generic "AnnotationKey" and "AnnotationValue" types in hopes that they'll be useful for more than just TLS options in the future.

Does this PR introduce a user-facing change?:

* TLS options keys are now subject to the same validation as Kubernetes annotations.
* TLS options values now have a max length of 1024 characters.

[howardjohn]

lgtm. Note your release note has "TCP" instead of "TLS"

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: howardjohn, robscott

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [robscott]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[youngnick]

Great change, just needs the docstring for AnnotationValue updated, then LGTM.

[youngnick]

/lgtm

/hold
for @jpeach

[jpeach]

/lgtm

[robscott]

/hold cancel