Pass --machine-type and --disable-autoconfig flags from driver to gcsfuse

[hungnguyen243]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test

/kind feature

/kind flake

What this PR does / why we need it:

This PR bumped gcsfuse binary to v2.12.0-gke-0, where the the new two mountOptions start to be supported. Note that gcsfuse receives these flags but will not turn on the default values until v3.

Summary of changes:

As part of GCSFuse's intelligent defaults, new mountOption flags are supported: --machine-type and --disable-autoconfig.
We want to pass these two flags over from the driver to GCSFuse in the following mechanism:

1. --machine-type: The driver has existing mechanism to get Node objects from K8s server starting from v1.14.0. We're fetching the node object inside NodePublishVolume, get the instance-type label,
2. --disable-autoconfig: This will be a new driver flag, defaulted to 'false', and added to driver's config, which is accessible from inside NodePublishVolume. This flag denotes whether gcsfuse will apply the machine-type based intelligent defaults.

Both flags are then written as a line-separated map to a temporary file under targetPath, which will be read by the sidecar container upon startup. The sidecar parses the file, reconstructs the map, and merges this map into the config file map. This approach is extensible, allowing us to add any new flag that we want to pass from the GCSFuse Driver container to the sidecar container and ultimately to the GCSFuse process.

Note that the PR also wraps the flag-writing logic on the driver behind a sidecar version filter, which checks that the sidecar container is a managed sidecar and on a compatible version (linked to a gcsfuse binary where the new flags are supported). This is to ensure that the file won't be unnecessarily written by the driver if not ultimately consumable by the sidecar (in the case of old/private sidecars). This minimum version is currently using a placeholder of v1.99.0-gke.0 in this PR, and we'll update this with the exact value after we completed the first round of release and get the corresponding sidecar image's version.

Testing:

Flag-passing functionality testing:

The PR has been tested both manually and with two new E2E tests by checking the GCSFuse config logged by the sidecar container:

1. Test that --machine-type and --disable-autoconfig=false (using driver's default value) are passed correctly to GCSFuse
2. Test that --machine-type and --disable-autoconfig=true (overwritten by the user pod's mountOptions) are passed correctly to GCSFuse

I ran these E2E tests with driver code built without the sidecar version filter, and made sure they're WAI: https://paste.googleplex.com/4777435008335872

Sidecar version filter testing:

1. Added unit tests for sidecar version check for all possible scenarios (compatible managed sidecar, old managed sidecar, private sidecar)
2. Tested that existing E2E tests for custom sidecars with an older gcsfuse tag are passing, and the flag file is not written by the driver (by checking driver's logs).

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Pass --machine-type and --disable-autoconfig flags to gcsfuse to enable intelligent defaults on GCSFuse for high-performance machine types.

[amacaskill]

I think we can remove this

[hungnguyen243]

Uncommented. This was left commented out during testing.