Post-release version bump to 2.0.35

* Automatically version from github.ref
* Build and test on windows, only sanity check run on others
* Build using desktop MSBuild: This is what appveyor does.
* Pack separately just the tools project.

This command also helps check the tool is installed properly and can run, returning a success status code, without having to repack anything actually.

Avoids having to skip it for the auto-generated .vs when you open a single project from the integration tests folder, for example

In order to test that the basics of the dotnet-ilrepack tool are working in all supported OSes, we pick a clean and common scenario that doesn't require any particular workload, and which builds fast, as a simple end-to-end sanity check for the global tool itself.

Note that the extensive tests already run on the code from existing tests is a prerequisite already for the test tool job.

This makes merging this PR to upstream can be done even if the GH workflows aren't used for publishing.

Provide a dotnet global tool version of ilrepack

Assembly strong name Linux compatibility

Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 3 to 4.1.7.
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](actions/download-artifact@v3...v4.1.7)

---
updated-dependencies:
- dependency-name: actions/download-artifact
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

…ub/workflows/actions/download-artifact-4.1.7

Bump actions/download-artifact from 3 to 4.1.7 in /.github/workflows