State what python version is used in README

[shenxianpeng]

Based on your description in #185, I've created this PR for you to review to close #185

We now have an additional place in the README that needs to be updated manually when Python version is upgraded

[2bndy5]

We now have an additional place in the README that needs to be updated manually when Python version is upgraded

We could use the permalink https://github.com/cpp-linter/cpp-linter-action/blob/bb0610e1deae636c111f86d8839c04b916ba67ef/action.yml#L120 which github would render as:

cpp-linter-action/action.yml

Line 120 in bb0610e

python-version: '3.10'

But we would still have to update the permalink if future changes to action.yml changes the line number.

[shenxianpeng]

The permalink explains why python 3.10 is better, perhaps less appropriate put it for the README. users can find out why with #185.
And the explanation you added “Our intention is to synchronize with the default python version included with Ubuntu latest LTS releases.” should be enough.

[2bndy5]

I'm going to push some changes...

• docker images not maintained by GitHub

  This seems like it is not a precise description (that's my mistake). I think "third-party docker images" might be better. Or maybe a direct link to the github docs about specifying a "job's container image" (which is different from the job's runner image).

• The placement of the note breaks the flow of paragraphs. I'm moving it up a bit.

[2bndy5]

Please hold off from merging this

The info provided isn't completely accurate to the current latest cpp-linter-action release (which uses py v3.11).

[2bndy5]

We should merge this only when we're ready to make a new release. We also have to satisfy #182 (with another round of testing).

[shenxianpeng]

The info provided isn't completely accurate to the current latest cpp-linter-action release (which uses py v3.11).

users who used cpp-linter-action@v2 already used python 3.10 when #186 was merged.

I made a mistake. Unless we create a new version, python 3.10 will apply to the new version tag and v2.