Ability to scale up runners with scaleUpFactor option

[akhilp6]

Checks

• [X] I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
• [X] I am using charts that are officially provided

Controller Version

0.9.3

Deployment Method

Helm

Checks

• [X] This isn't a question or user support case (For Q&A and community support, go to Discussions).
• [X] I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes

To Reproduce

Check the in the gha-runner-scale-set chart, there's no way to set `sclaeUpFactor in `values.yaml` for the actions.github.com_autoscalingrunnersets.yaml

Describe the bug

Currently the runners scales up based on the count of jobs requested. For example, let say if we get a 5 new job request then it basically add 5 new runners. This approach is increasing our start up time as it basically queue up until all the runners are started. We would like to have some kind of scaleUpFactor option which would basically pre-load the runners which would help in decreasing the start up time.

Describe the expected behavior

N/A

Additional Context

N/A

Controller Logs

N/A

Runner Pod Logs

N/A

[xunholy]

@akhilp6 how does this differ from minRunners? Is the idea you'd always create slightly more than the queue depth on Github?