detailed docs separate and then merge the webhook server and controller

[jorhett]

In the webhook driven scaling docs, it correctly distinguishes the existence of the webhook server as a separate component https://github.com/actions-runner-controller/actions-runner-controller/blob/master/docs/detailed-docs.md?plain=1#L704

However, in the explanation of how it comes together the operations which would be done by the webhook server are said to be done by the controller process: https://github.com/actions-runner-controller/actions-runner-controller/blob/master/docs/detailed-docs.md?plain=1#L734-L739

1. GitHub sends a workflow_job event to ARC with status=queued
2. ARC finds a HRA with a workflow_job webhook scale trigger that backs a RunnerDeployment / RunnerSet with matching runner labels
3. The matched HRA adds a unit to its capacityReservations list
4. ARC adds a replica and sets the EffectiveTime of that replica to current + HRA.spec.scaleUpTriggers[].duration

The detailed docs would be significantly more valuable if this is clarified. According to what I read from this, the controller is instantly made aware of the change. However in reviewing the implementation, it appears that the controller isn't aware of the change until it polls the HRA at the configured sync time?