Add Priority ENV for gitlab yaml

[NorseGaud]

Need a way to set priority for the gitlab yaml/repo/project instead of just on registration for the runner

--anka-controller-address value       Anka Cloud Controller address (example: http://anka-controller.mydomain.net[:8090]) [$CONTROLLER_ADDRESS]
   --anka-template-uuid value            Specify the VM Template UUID [$TEMPLATE_UUID]
   --anka-tag value                      Specify the Tag to use [$TAG]
   --anka-node-id value                  Specify the Node ID to run the job (you can find this in your Controller's Nodes page) [$NODE_ID]
   --anka-priority value                 Set the job priority [$PRIORITY]
   --anka-node-group value               Limit jobs to a specific node group (accepts name or ID) [$NODE_GROUP]
   --anka-root-ca-path value             Specify the path to your Controller's Root CA certificate [$ROOT_CA_PATH]
   --anka-cert-path value                Specify the path to the GitLab Certificate (used for connecting to the Controller) (requires you also specify the key) [$CERT_PATH]
   --anka-key-path value                 Specify the path to your GitLab Certificate Key (used for connecting to the Controller) [$KEY_PATH]
   --anka-controller-http-headers value  In JSON format, specify headers to set for the HTTP requests to the controller (quotes must be escaped) (example: "{ "HOST": "testing123.com", "CustomHeaderName": "test123" }") [$CONTROLLER_HTTP_HEADERS]
   --anka-skip-tls-verification          Skip TLS Verification when connecting to your Controller [$SKIP_TLS_VERIFICATION]
   --anka-keep-alive-on-error            Keep the VM alive for debugging job failures [$KEEP_ALIVE_ON_ERROR]

[NorseGaud]

I'm actually going to avoid implementing this for the following reason: Administrators of the CI/CD pipeline don't necessarily want users to be able to control a priority. This can cause a team to request more than they are allowed in larger environments and generate a whole slew of problems. If anyone really wants this, please let us know.