(fix): Add TektonScheduler, syncerservice and TektonMulticlusterProxyAAE CRDs to Helm chart

[mbpavan]

With the current Helm chart, installing the operator with installCRDs=true does not create the TektonScheduler, syncerservice and TektonMulticlusterProxyAAE CRDs. This fixes helm install and upgrades

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Run make test lint before submitting a PR
• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Testing

Fresh install (Kubernetes) works fine

Release Notes

NONE

[mbpavan]

/kind bug

[pramodbindal]

/lgtm

[anithapriyanatarajan]

@mbpavan - Do we need the syncer service as well? Also why are we not using the /cherry-pick automation please? Could we try that after merging #3265

[mbpavan]

@mbpavan - Do we need the syncer service as well? Also why are we not using the /cherry-pick automation please? Could we try that after merging #3265

@anithapriyanatarajan added syncer service.
Ideally, this should have been cherry-picked before the operator release process. The files here have version 0.79, while the main branch contains devel. Because of this mismatch, I created a separate PR instead of using a cherry-pick, as the cherry-pick bot might encounter merge conflicts due to the version difference which we might need to do manually due to merge conflitcs. To avoid that, I created this PR directly

[anithapriyanatarajan]

@mbpavan - Do we need the syncer service as well? Also why are we not using the /cherry-pick automation please? Could we try that after merging #3265

@anithapriyanatarajan added syncer service. Ideally, this should have been cherry-picked before the operator release process. The files here have version 0.79, while the main branch contains devel. Because of this mismatch, I created a separate PR instead of using a cherry-pick, as the cherry-pick bot might encounter merge conflicts due to the version difference which we might need to do manually due to merge conflitcs. To avoid that, I created this PR directly

@mbpavan - Thanks for clarifying. I missed this aspect.

[anithapriyanatarajan]

/lgtm

[anithapriyanatarajan]

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anithapriyanatarajan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [anithapriyanatarajan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment