[Pylint] override scoring to include info warnings

[l0lawrence]

fixes #2802

default pylint scoring is: (max(0, 0 if fatal else 10.0 - ((float(5 * error + warning + refactor + convention)/ statement) * 10)))

adding in +info

[iscai-msft]

ooh perfect, thank you so much @l0lawrence, the CI is now failing which is good. Going to take a look at this later today

[l0lawrence]

Hi @msyyc, @tadelesh I think @iscai-msft is OOF, if you get a chance could you please take a look at the pylint warnings here?

They are related to this issue:#2802

[msyyc]

Hi @msyyc, @tadelesh I think @iscai-msft is OOF, if you get a chance could you please take a look at the pylint warnings here?

They are related to this issue:#2802

Sure. Now we are migrating some code to https://github.com/microsoft/typespec/tree/main/packages/http-client-python which has strict ETA so we will take a look after the migration done.

[iscai-msft]

The migration issue should also solve the pylint issues, since I fixed the pylint issues in the unbranded emitter. We have updated the branded emitter (the existing one we use to generate azure code) to depend fully on the unbranded emitter, so the code emitted by it should have the pylint issues solved. There is some issue with migrating the tsp-client update to the version with the fixed pylint issues, so we haven't published it in azure-sdk-for-python repo yet, but once that is done, the pylint issues should be fixed. I'm working on that issue today

[msyyc]

move to #2876