Sort elements going into cache keys

[brynary]

I noticed locally that in some cases that config files were being added to the cache key in a different order, which produces different cache results. I audited the cache key generation code for iteration and added explicit sorting to try to increase determinism.

[qltysh]

The code coverage on the diff in this pull request is 0.0%

Drilldown

Path	File Coverage Δ
qlty-check/src/cache.rs	-0.0
qlty-check/src/tool/command_builder.rs	2.6
qlty-config/src/library.rs	-0.7
qlty-cli/src/initializer/scanner/gemfile.rs	-0.3
qlty-check/src/tool/ruby/sys/macos.rs	3.1
qlty-cli/src/telemetry/segment.rs	0.0
qlty-check/src/tool/download.rs	0.7
qlty-config/src/workspace.rs	-9.0
qlty-check/src/tool/ruby/sys/linux.rs	-1.6
qlty-cli/src/telemetry/analytics.rs	0.0