Sort enabled/disabled Pylint warning lists

[SpecLad]

Motivation and context

Makes them easier to navigate.

How has this been tested?

Checklist

• [x] I submit my changes into the develop branch
• ~~[ ] I have created a changelog fragment~~
• ~~[ ] I have updated the documentation accordingly~~
• ~~[ ] I have added tests to cover my changes~~
• ~~[ ] I have linked related issues (see GitHub docs)~~

License

• [x] I submit my code changes under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.76%. Comparing base (1a971f7) to head (2d3dec2). Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #9532   +/-   ##
========================================
  Coverage    73.76%   73.76%           
========================================
  Files          448      448           
  Lines        46678    46698   +20     
  Branches      3942     3942           
========================================
+ Hits         34430    34445   +15     
- Misses       12248    12253    +5     

Components	Coverage Δ
cvat-ui	77.75% <0.00%> (-0.02%)	:arrow_down:
cvat-server	70.65% <89.47%> (+0.01%)	:arrow_up:

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.