Avoid using CI run counter for FileVersion

[glopesdev]

According to the documentation for FileVersion the resolution for individual components of the version number is 16-bit.

It might take a while still to hit the max 65535 value judging from the rate at which we are currently burning through CI in both individual commits to branches and PRs, but still I was wondering whether there might be a better approach to incrementing the revision counter. I was also interested in having a number that would somehow relate to how far away we are from the last release.

It looks like python CI wheels automatically set both dev and ci counter suffixes to match the number of commits since last tag, which seems pretty reasonable. To resolve clashes using this counter in package IDs they append also the commit hash using +sha8abcd for example.