The Kubernetes documentation that you pointed out is NOT correct and should be modified since the master actually scales.
First of all notice that how and when Google Cloud takes care of resizing the master should not be a concern for users if the behaviour of the cluster is stable and performant.
It is a managed service and therefore some details are not public, for example how the master is resized and which algorithms are used are not shared.
Moreover there is no information or disclaimer regarding the machine type of the master in the autoscaler GKE official documentation and it if the master was not able to resize since it would have been an action potentially disruptive for the cluster health.
From the blog
"Master VM is automatically scaled, upgraded, backed up and secured"
However if you want you can test the behavior:
Create a cluster having one node
Add 10 nodes
The master will be not reachable for a moment and a call to the API will resolve in an error
$ gcloud container clusters get-credentials cluster-1 --zone us-central1-a --project **-**
Fetching cluster endpoint and auth data.
WARNING: cluster cluster-1 is not running. The kubernetes API may not be available.
Inspect the logs, you will notice that in the logs will be present an entry "master upgrade"
There is an feature request asking to Improve the Google cloud documentation, you can decide to star it in order to receive updates.
On the other hand to fix the Kubernetes documentation I opened a public issue on Github.