SPL-298478: Add App CRD on M1 milestone branch

[jzywiecki]

Description

This PR adds the new App custom resource definition to the operator.

Key Changes

• Added the new App API type under enterprise.splunk.com/v4
• Generated and registered the App CRD
• Added a sample App manifest and wired it into sample kustomization
• Regenerated deepcopy and CRD artifacts to reflect the final schema

Testing and Verification

• Regenerated manifests and deepcopy code with make manifests generate
• Verified the API changes
• Checked the generated CRD schema for the new spec and status fields
• Manual testing of creating the CR

Fields that must be set validation:

appID: Unique identifier of the application

version: Desired application version

targetRef:

kind

name

sourceRef: Reference to an AppSource resource

package:

path: Path to the application package within the source

scope: Deployment scope definition

Related Issues

• SPL-298478

Screenshots

PR Checklist

• Code changes adhere to the project's coding standards.
• Relevant unit and integration tests are included.
• Documentation has been updated accordingly.
• All tests pass locally.
• The PR description follows the project's guidelines.

[naimulh247]

There are some merge conflicts, can we rebase and push again

[naimulh247]

we might want to consider using pointers as part of the app_types.go to know if user defined the field or not

[vivekr-splunk]

I found two blocking issues in the current App CRD/controller shape.