Use alternative 'upstream' for driver bindings

[gbraad]

It's suggested to use htps://github.com/machine-drivers/vz as the upstream for the bindings.

Ref:

• [Action] Considering an alternative upstream for continued improvements on vfkit crc#3362

Perhaps it might even be beneficial if parts of this codebase becomes part of the machine-drivers codebase?

[afbjorklund]

I don't think that the "machine-drivers" organization is a good place to host upstream dependencies.

• Why was this fork created ? machine-drivers/vz#1

I think that the fork should be archived, at least until a docker-machine-driver-vfkit exists...

And it is unlikely to do so, since there is/was no support for arm64 in the boot2docker iso.

[afbjorklund]

You could of course use crc-org/vz, if you need to fork... But machine-drivers is retiring soon.

Since it (docker/machine) has not been updated since 2019, it probably will see EOL in 2024.