Revert pinning of click package for scancode installation

[mthalman]

Once aboutcode-org/scancode-toolkit#4369 is fixed and we get a new release of scancode with the fix, we should remove the pinning of the click package that was done as a workaround for this issue:

• Upgrade scancode to 32.3.3 and downgrade click to 8.1.8 sdk#49047 (9.0)
• Upgrade scancode to 32.3.3 and downgrade click to 8.1.8 installer#20445 (8.0)

[MichaelSimons]

@mthalman - what is the long term plan now that we have transitioned to using a container? Should the containers use a floating version? I see that aboutcode-org/scancode-toolkit#4369 has been addressed. Can this issue be moved out of 'Blocked'?

[mthalman]

Long term is not to do anything with click at all. In other words, revert the line which explicitly installs it. It'll get installed automatically as a dependency.

This is still blocked until a new release of scancode is available with this fix.

[Winniexu01]

release/8.0.1xx pipeline run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2740700&view=results release/9.0.1xx pipeline run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2740698&view=results
main pipeline run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2740749&view=results

After upgrading Scancode from 32.3.3 to 32.4.0, several license detection rules changed in the new version, causing license scan results for many files to be different from the previous results.

Update license scan tests baseline and exclusions:
release/8.0.1xx pipeline run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2744312 (internal Microsoft link)
release/9.0.1xx pipeline run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2744297 (internal Microsoft link)
main pipeline run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2744301 (internal Microsoft link)