TLSPK Agent / Jetstack Agent (Re-branding)

## History

For anyone who doesn't know, what was formerly Jetstack Secure (which used the Jetstack Agent) is now known as TLS Protect for Kubernetes (TLSPK) (which also uses the Jetstack Agent).

## Issue

I've had the same conversation at least 3 times now about renaming "X" to TLSPK. Where "X" is the name of the chart, the namespace we install into, etc. Obviously it causes some confusion and should be standardised. So here's the issue to discuss it.

## Main Concern & Assumption

Changing the helm chart name, or the readme is not enough as the confusion or contradiction continues. There's the domain we host on and the organisation we host this project under.

TLS Protect for Kubernetes is a [Venafi](https://venafi.com/tls-protect-for-kubernetes/) and the assumption is that the entire product including this agent would be re-branded to be consistent throughout.

### Impacted resources

- The domain we host on: https://platform.jetstack.io/
- The GitHub organisation this repository lives under, "[Jetstack](https://github.com/jetstack)"
- The name of [this repository](https://github.com/jetstack/jetstack-secure)
- The [readme](https://github.com/jetstack/jetstack-secure#readme) of this repository
- The [chart](https://github.com/jetstack/jetstack-secure/tree/master/deploy/charts/jetstack-agent) we have added

(possibly more, ran out of ideas)

## Ideal Scenario

We work with the TLSPK product team to sort out what the end result should be and standardise around that. That could be: `venafi/tlspk-agent`. Until we know what the right naming should be, any work to rename parts could well be wasted effort.

## What's next

I'd like to use this thread just to give some clarity to the open source side of Jetstack Secure / TLS Protect for Kubernetes around the terminology and branding here.