Investigate / review / setup node selection logic

[vexingly]

The nodepools will be updated in #1967 but we will require some logic for node selection.

1. Keep existing logic for notebooks that have higher than 14 CPU to be launched on the "usercpuXXxx" nodes
2. Add taint/toleration for scheduling OpenM++ jobs to use these larger CPU based nodes
3. Investigate other methods for scheduling different scenarios? The UAT will provide more details on how users schedule their jobs that could be helpful for working out a longer term strategy

Existing logic for notebooks is here: https://github.com/StatCan/aaw-toleration-injector/blob/main/mutate.go