Handle Namespace v1 in the uptest run

[ytsarev]

Description of your changes

• Special skip of the Namespace object similar to Secret
• Fixes Uptest need to skip Namespaces/v1 similar to Secrets/v1 #18

I have:

• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

make test
13:39:30 [ .. ] go test unit-tests
?   	github.com/crossplane/uptest/internal/config	[no test files]
	github.com/crossplane/uptest/cmd/uptest		coverage: 0.0% of statements
	github.com/crossplane/uptest/internal		coverage: 0.0% of statements
?   	github.com/crossplane/uptest/internal/version	[no test files]
ok  	github.com/crossplane/uptest/internal/templates	(cached)	coverage: 76.5% of statements
?   	github.com/crossplane/uptest/internal/config	[no test files]
	github.com/crossplane/uptest/internal		coverage: 0.0% of statements
	github.com/crossplane/uptest/cmd/uptest		coverage: 0.0% of statements
?   	github.com/crossplane/uptest/internal/version	[no test files]
=== RUN   TestRender
=== RUN   TestRender/SuccessSingleResource
=== RUN   TestRender/SuccessMultipleResource
--- PASS: TestRender (0.00s)
    --- PASS: TestRender/SuccessSingleResource (0.00s)
    --- PASS: TestRender/SuccessMultipleResource (0.00s)
=== RUN   TestRenderWithSkipDelete
=== RUN   TestRenderWithSkipDelete/SuccessSingleResource
=== RUN   TestRenderWithSkipDelete/SkipImport
=== RUN   TestRenderWithSkipDelete/SuccessMultipleResource
--- PASS: TestRenderWithSkipDelete (0.00s)
    --- PASS: TestRenderWithSkipDelete/SuccessSingleResource (0.00s)
    --- PASS: TestRenderWithSkipDelete/SkipImport (0.00s)
    --- PASS: TestRenderWithSkipDelete/SuccessMultipleResource (0.00s)
PASS
coverage: 76.5% of statements
ok  	github.com/crossplane/uptest/internal/templates	0.566s	coverage: 76.5% of statements
13:39:35 [ OK ] go test unit-tests

e2e test

Using https://github.com/upbound/configuration-azure-network as a base sample material. Adding Namespace to the test example:

diff --git a/examples/network-xr.yaml b/examples/network-xr.yaml
index d05c7e4..8c84b10 100644
--- a/examples/network-xr.yaml
+++ b/examples/network-xr.yaml
@@ -6,3 +6,8 @@ spec:
   parameters:
     id: ref-azure-network-from-xr
     region: westus
+---
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: test-namespace

and running standard make e2e

Before the PR change
Everything is ready

k get managed
NAME                                                     SYNCED   READY   EXTERNAL-NAME             AGE
resourcegroup.azure.upbound.io/ref-azure-network-bm8fx   True     True    ref-azure-network-bm8fx   8m35s

NAME                                                                     SYNCED   READY   EXTERNAL-NAME                    AGE
virtualnetwork.network.azure.upbound.io/ref-azure-network-from-xr-vnet   True     True    ref-azure-network-from-xr-vnet   8m35s

NAME                                                           SYNCED   READY   EXTERNAL-NAME                  AGE
subnet.network.azure.upbound.io/ref-azure-network-from-xr-sn   True     True    ref-azure-network-from-xr-sn   8m35s

But uptest is in endless loop waiting for Namespace readiness and never completes(until timeout failure)

error: timed out waiting for the condition on namespaces/test-namespace

After this PR change

I inject local uptest build from this PR into the Configuration tools cache

cp ~/uptest/_output/bin/darwin_arm64/uptest ./.cache/tools/darwin_arm64/uptest-v0.11.1

and running make e2e again

--- PASS: kuttl (269.16s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/case (268.66s)
PASS
14:31:06 [ OK ] running automated tests

[sergenyalcin]

Thanks @ytsarev LGTM!

[CasperGN]

@ytsarev the oidc-cookie-secret now depends on this change. More context in the internal PR.