SSH key permissions error after machine boots up in vagrant

[crypt0ace]

Testing out the V3. Great work. There's an slight problem with Vagrant correctly setting up permissions on the SSH key file. Its not an issue but more like annoying because during the first install its required to constantly change the permissions manually on the key file until all 5 machines in GOAD are provisioned using vagrant. I'm using it on windows using WSL. If its possible to add the command before vagrant uses SSH, it will save some time.
The command that needs to be run is the following.

chmod 600 /mnt/g/Vagrant/.vagrant.d/insecure_private_keys/vagrant.key.ed25519

[Mayfly277]

it is a vagrant issue.
i think the solution is here : hashicorp/vagrant#8742 (comment)

export VAGRANT_WSL_WINDOWS_ACCESS_USER_HOME_PATH="/mnt/g/Vagrant/"

I keep the issue open to see if i can automatically change that in goad