Change handling of time in ctl integration tests
Change handling of time in ctl integration tests

Two main changes:

1. Timezones

Because the tests were run in bazel or in CI environments, they always
ran in UTC, but the behaviour of ctl is based on local time, not UTC. We
show "not after" in the local timezone.

Now, we parse the "not after" time from the output so that its timezone
is respected and should pass on any developer laptop even outside of
bazel.

2. Created At

There was previously a pretty big regex for checking that "Created at"
was a valid timestamp. Now, we simply parse the timestamp using the Go
standard library to confirm that it's a valid RFC3339 timestamp.

Signed-off-by: Ashley Davis <2a98ad09b55d7402451cbad533f334a828c02124@jetstack.io>

cert-manager/cert-manager,jetstack/cert-manager,cert-manager/cert-manager,jetstack/cert-manager,cert-manager/cert-manager,jetstack/cert-manager