Add complete k8s object validation and defaults on standalone

[mtardy]

See individual commits.

This PR actually uncovered a few issues/bugs in type declaration and TracingPolicy tests. We will now have the same custom resource validation and defaults when deploying on k8s using CRD mechanisms and in standalone, this should unify the behavior.

Code addition is huge because we needed to make a binary an independent Go module because of a version mismatch in a library and I vendored the dependencies.

This might break user workflow if they relied on the fact that the validation was not properly done on standalone.

[mtardy]

I linked this PR to close #1318 as well because trying to decode the content of examples/tracingpolicy is already done here:

tetragon/pkg/tracingpolicy/generictracingpolicy_test.go

Lines 456 to 488 in 9405281

	func TestExamplesSmoke(t *testing.T) {
	_, filename, _, _ := runtime.Caller(0)
	examplesDir := filepath.Join(filepath.Dir(filename), "../../examples/tracingpolicy")
	err := filepath.Walk(examplesDir, func(path string, info os.FileInfo, err error) error {
	if err != nil {
	return err
	}
	// Skip non-directories
	if info.IsDir() {
	return nil
	}
	// Skip non-yaml files with a warning
	if !strings.HasSuffix(info.Name(), "yaml") || strings.HasSuffix(info.Name(), "yml") {
	logger.GetLogger().WithField("path", path).Warn("skipping non-yaml file")
	return nil
	}
	// Fill this in with template data as needed
	data := map[string]string{
	"Pid": fmt.Sprint(os.Getpid()),
	}
	// Attempt to parse the file
	_, err = fileConfigWithTemplate(path, data)
	assert.NoError(t, err, "example %s must parse correctly", info.Name())
	return nil
	})
	assert.NoError(t, err, "failed to walk examples directory")
	}

But with this PR it will actually now pass a proper validation step while decoding FromYAML.

[mtardy]

Followups would be:

• Improve the state of PreValidate for kprobes and add something more standard that we can share for advanced validation between kprobes/tracepoints/uprobes with specific validation for each of them, outputting format similar to what k8s validation does.
• Add advanced pre validation in smoke test

[kevsecurity]

If it's all green, then I think it's good to go.