fix(inputs.sqlserver): More precise version check

[spaghettidba]

Some queries do not work with 2008R2 RTM, but they need at least SP2
Queries changed:

• sqlServerProperties

• sqlServerVolumeSpace

• Updated associated README.md.

• Wrote appropriate unit tests.

• Pull request title or commits are in conventional commit format

[srebhan]

@Trovalo can you please take a look!?

[Trovalo]

The PR is ok,
It will avoid execution errors on the oldest versions of SQL Server (supported by Telegraf).

@srebhan do we also need to create an issue or having just the PR is fine?
(not sure about what "Semantic PR and Commit Messages" means, is there a check over the PR text itself?)

[telegraf-tiger]

Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip.
Downloads for additional architectures and packages are available below.

☺️ This pull request doesn't significantly change the Telegraf binary size (less than 1%)

📦 Click here to get additional PR build artifacts

Artifact URLs

DEB	RPM	TAR GZ	ZIP
amd64.deb	aarch64.rpm	darwin_amd64.tar.gz	windows_amd64.zip
arm64.deb	armel.rpm	darwin_arm64.tar.gz	windows_arm64.zip
armel.deb	armv6hl.rpm	freebsd_amd64.tar.gz	windows_i386.zip
armhf.deb	i386.rpm	freebsd_armv7.tar.gz
i386.deb	ppc64le.rpm	freebsd_i386.tar.gz
mips.deb	riscv64.rpm	linux_amd64.tar.gz
mipsel.deb	s390x.rpm	linux_arm64.tar.gz
ppc64el.deb	x86_64.rpm	linux_armel.tar.gz
riscv64.deb		linux_armhf.tar.gz
s390x.deb		linux_i386.tar.gz
		linux_mips.tar.gz
		linux_mipsel.tar.gz
		linux_ppc64le.tar.gz
		linux_riscv64.tar.gz
		linux_s390x.tar.gz
		static_linux_amd64.tar.gz

[srebhan]

@Trovalo I think the text in the PR is clear enough to not requiring an issue, what do you think @powersj?

Regarding the "Semantic PR..." error, it comes from the fact that this PR has only one commit, so the commit also needs to adhere to the semantic PR standards... We can fix this manually on this PR, but please keep this in mind for future PRs @spaghettidba!

[srebhan]

@spaghettidba can you please try to rebase this PR on the latest master to (hopefully) get CircleCI to retry?!?

[spaghettidba]

Sorry, I have no idea how to do that. My GitHub abilities are extremely limited.
Could you please help me?

[Trovalo]

Running git rebase master or git rebase master _YourbranchName_ should suffice... but since the original repo has been deleted that's not possible.
Honestly, I'm not sure about how to "fix" this... can we edit the commit message and force CircleCI to run again? or do we need a "clean" PR (meaning closing this one and replicating it in a new one)?

[srebhan]

Thanks @spaghettidba for the fix! Given that this seems not to touch any go-code, I'm also find with just merging it as-is. @powersj what do you think?