Update API types to comply with new Kubernetes API conventions

## Summary
Update bpfman-operator CRD API types to comply with new Kubernetes API conventions as outlined in [kubernetes/community#8486](https://github.com/kubernetes/community/pull/8486) and OpenShift API linter requirements.

## Context
Recent updates to Kubernetes API conventions require:
- All fields must have `omitempty` tags
- Optional fields in aggregated APIs (those with protobuf tags) must use pointers
- Complete validation rules for all string and list fields
- `omitzero` tags for struct fields where appropriate

## Current State
Our APIs are partially compliant but need systematic updates across:
- `apis/v1alpha1/shared_types.go`
- `apis/v1alpha1/*_types.go` (all program type files)
- Validation rules are incomplete for many fields

## Proposed Changes
1. **Field Tags**: Add `omitempty` to all fields
2. **Pointer Usage**: Convert optional fields to pointers in aggregated APIs
3. **Validation**: Add MinLength/MaxLength to strings, MinItems/MaxItems to arrays
4. **Struct Validation**: Add MinProperties for structs with all optional fields

## References
- [Kubernetes API Conventions PR #8486](https://github.com/kubernetes/community/pull/8486)
- OpenShift API linter enforcement

Start with apis/v1alpha1/shared_types.go and the apis/v1alpha1/*_types.go program files, then compare their tags, pointer usage, and validation markers with Kubernetes API conventions PR #8486 and OpenShift API linter requirements. Done means the affected fields follow the stated omitempty, pointer, string/list validation, and struct validation rules across the API types.

Written by the indexing model from the issue text.