Install additional Android SDKs on Windows runners

**Context**

On Windows runners, using a target Android SDK version lower than one shipped with Unity gives an error, e.g. targeting SDK 32 with Unity 2022.3 which is required for Meta Quest:

```
##[error]UnityException: Target Android SDK not installed
Android SDK does not include your Target SDK of 32.
```

This occurs even when specifying `AndroidTargetSdkVersion: AndroidApiLevel32` as a parameter in the workflow.

Linux runners take care of this, due to #582 being implemented in response to #581

Additional context: I prefer to maintain a fleet of WIndows runners to allow Windows IL2CPP builds of a different project.

**Suggested solution**

Invoke the sdkmanager, similarly to #582

**Additional details**

[Discord thread](https://discord.com/channels/710946343828455455/1288459471714259007)

Start by reviewing the Linux SDK-installation change from #582 and the workflow path that handles Android SDK setup on Windows runners. Invoke sdkmanager for the requested target SDK, including AndroidApiLevel32, then verify that a Windows Unity build using a lower target SDK completes without the “Target Android SDK not installed” error.

Written by the indexing model from the issue text.