PowerConfig CR not being very useful

Currently PowerConfig CR has only 1 role, deploying PowerNodeAgent onto accordingly labeled nodes. Upside is that expected label can be modified in the CR and should be dynamically reconciled in case of changes. Downside is that we have additional CR that does only that. As we experienced ourselves, the lesser number of CRs, the easier getting familiar with product is, and this is even more true for end users.

Extended PowerProfiles feature which was a thing for KPM in the past were already deleted before we took ownership, so passing names of the EPP derived profiles in it also doesnt make much sense.