Setup recurring runs for Harvester

[slickwarren]

Depends on merging harvester client and #1617

• provisioning (rke2, k3s), permute on cni for rke2:
  • node driver
  • custom
  • imported
  • scale up/down
  • multiple clusters at once in rancher from harvester
  • drain nodes (rke2 only)
• rancher upgrade
• rbac -- TBD (working with harvester team to find out more)
• charts -- TBD (working with harvester team to find out more)

[slickwarren]

Testing the following to prepare PR:

• recurring runs jenkinsfile setup to run in vpn -- get to running state where all stages trigger correctly
• ^ + individual job - get to running state where all stages trigger correctly
• make sure cleanup is working on recurring runs / individual job for:
  • harvester resources
  • jenkins agent resources
• pulls from prime registry / helm repo
• get gluecode to work with harvester
  • requires running code that hasn't merged yet: register harvester cluster with rancher setup in order to use harvester as a provider
  • will require running 'harvester registration with rancher' as its own stage in order to provision later
• get harvester provider to provision via rancher
  • requires running code that hasn't merged yet: register harvester cluster with rancher setup in order to use harvester as a provider
  • will require running 'harvester registration with rancher' as its own stage in order to provision later
• anything else?

[slickwarren]

note; merging this will be on hold until we figure out where our codebase will live -- and when the harvester PR will be merged.