Upgrade attohttpc and use native root certificates

[charlespierce]

Closes #1364

Info

• Prior to version 0.24.0, when using the tls-rustls feature flag, attohttpc would use WebPKI root certificates instead of the native certificate store for the appropriate system.
• As a result, when we switched in Volta 1.1.0 to use rustls instead of native-tls, we regressed in our certificate handling, causing issues with corporate proxies.
• In version 0.24.0, attohttpc added the ability to use native root certificates with rustls via the rustls-native-certs crate.
• This allows the root certificate finding to match that of the native-tls implementation.

Changes

• Updated our imports of attohttpc to use version 0.24 and activate the tls-rustls-native-roots feature flag, to ensure that we are using the expected certificate stores for our network connections.

Tested

• I don't have an easy way to test the native certificates themselves, however I did run the smoke tests locally to ensure that our connections continue to work in the public case.
• Will likely need to confirm with the original issue reporter to verify that this change resolves the issue (once it's released).

[Purexo]

Hello, I just seen this PR. I will take time tomorrow to test it.

Because I originally done this one #1365

I can't wait to have native ssl store support in this tool, with this, I will migrate with my teams from nvm-windows to volta at the next release !

[Purexo]

Seems OK, after full uninstall volta (from windows params + remove appdata volta folder and program files volta folder) and

git pull upstream main
cargo wix --nocapture --package volta --output target\wix\volta-windows.msi

Then run the msi

my node / npm commands is working perfectly from volta proxy, with the installation of rights versions of node and npm from package.json volta key.

Yes i'm behind a MITM Proxy enterprise so the CA certs needs to be loaded from the native ssl store.

@charlespierce, can I ask when is plan the next release ?