feat(issue 27): CLI CRUD for namespaces after updates to policy config schema refactoring

[jakedoublev]

1. Adds full CLI/handlers CRUD for namespaces
2. updates go.mod to use local modules for opentdf-v2-poc for ease of development until schema rework is merged with main in github
3. comments out attributes work so far until schema rework is brought in so the build/run does not fail

Addresses #27

[alkalescent]

Getting an error when installing or running:

pkg/handlers/namespaces.go:4:2: no required module provides package github.com/opentdf/opentdf-v2-poc/sdk/namespaces; to add it:
	go get github.com/opentdf/opentdf-v2-poc/sdk/namespaces

[jakedoublev]

Getting any error when installing or running:

pkg/handlers/namespaces.go:4:2: no required module provides package github.com/opentdf/opentdf-v2-poc/sdk/namespaces; to add it:
	go get github.com/opentdf/opentdf-v2-poc/sdk/namespaces

@suchak1
Yes, unfortunately that is expected because of how Go resolves modules while the namespaces work lives on a branch other than main. This workaround allows you to have the opentdf-v2-poc repo in the same level directory on your machine, and if you run git fetch, then switch to branch policy-config-changes or another branch off of that secondary trunk containing the schema rework, you will be able to run go get github.com/opentdf/opentdf-v2-poc/sdk/namespaces and have it be found.

This is unfortunately the downstream impact of consuming services on a specific branch in another repo while they're unmerged.

It's the equivalent of having your package.json version for a dependency pointing to a local filepath.

[alkalescent]

Gotcha, I was able to run the CLI while having that branch checked out