This is coming from https://issues.redhat.com/browse/SRVKP-3347

Right now, we are keeping all the old version clustertasks installersets with operator upgrade, like if some user has upgraded from 1.6 to 1.12, user will see all the versioned clustertask installersets from 1.6 to 1.12

This can create issues when in future released, things gets removed/deprecated like resources has been removed. clustertask itself as been deprecated etc.

We should keep some old versioned clustertask but not keep all.

Suggestions from refinement call
1. Keep last 3 version or some other pre decided number
2. Keep only supported version
3. Remove installerset, but keep clustertask on cluster

We need to discuss and figure out a conclusion so that we don't face issues like https://issues.redhat.com/browse/SRVKP-3347