Statically link to the C runtime in MSVC

[saulecabrera]

Description of the change

Javy version 1.4.0 statically linked to the C runtime. Such version was built with Rust 1.75.

Javy version 2.0.0, built with Rust 1.79.0, which doesn't perform static linking by default. This commit adds a directive to preserve the same behavior as in v 1.4.0.

Checklist

• I've updated the relevant CHANGELOG files if necessary. Changes to javy-cli and javy-core do not require updating CHANGELOG files.
• I've updated the relevant crate versions if necessary. Versioning policy for library crates
• I've updated documentation including crate documentation if necessary.

[saulecabrera]

Testing

The best way to test this change at this time is to download the Windows executable available in my fork and make sure that it runs correctly e.g. javy --version.

I considered adding a CI step, but unfortunately there are several considerations:

1. All Windows runners are pre-provisioned with Visual C++, and apparently: (i) there's no way to uninstall it (ii) there's no way to configure GitHub Actions to provide a fresh runner, without any dependencies. Additionally the GitHub Actions team is not planning on supporting this feature.. The recommended way to modify Windows runners is through Chocolatey, but as far as I investigated, it can't be used uninstall Visual C++ (not surprising).
2. The recommended approach, as per the link in the previous point is to introduce a custom runner. Which we could adopt if we wanted to, and if we do, my suggestion would be to do it a follow up PR. But generally speaking, the change in this PR is probably enough. If this issue were to happen again, there's a very easy fix that users can apply, which is installing Visual C++.

[jeffcharles]

Tested on my Windows PC without Visual Studio and it seems to work. I probably have a bunch of redistributable Visual Studio dlls installed but not really sure how to be more certain within a reasonable amount of time.