SONARPY-2864 Create rule S7510 The \"sorted\" function call should not be passed to the \"reversed\" function as an argument

rules/S7510/metadata.json

@@ -0,0 +1,2 @@
+{
+}

rules/S7510/python/metadata.json

@@ -0,0 +1,23 @@
+{
+  "title": "The \"sorted\" function call should not be passed to the \"reversed\" function as an argument",
+  "type": "CODE_SMELL",
+  "status": "ready",
+  "remediation": {
+    "func": "Constant\/Issue",
+    "constantCost": "1min"
+  },
+  "tags": [
+  ],
+  "defaultSeverity": "Major",
+  "ruleSpecification": "RSPEC-7510",
+  "sqKey": "S7510",
+  "scope": "All",
+  "defaultQualityProfiles": ["Sonar way"],
+  "quickfix": "unknown",
+  "code": {
+    "impacts": {
+      "MAINTAINABILITY": "MEDIUM"
+    },
+    "attribute": "CONVENTIONAL"
+  }
+}

rules/S7510/python/rule.adoc

@@ -0,0 +1,31 @@
+This rule raises an issue when the `reversed()` function is called with a `sorted()` as an argument.
+
+== Why is this an issue?
+
+The `sorted()` function has a `reverse` parameter that provides the same functionality as the `reversed()` function.
+
+== How to fix it
+Use the `reverse` parameter of the `sorted()` function to sort in descending order instead of using `reversed()`.
+
+=== Code examples
+
+==== Noncompliant code example
+
+[source,python,diff-id=1,diff-type=noncompliant]
+----
+data = [3, 1, 4, 1, 5, 9]
+result = reversed(sorted(data)) # Noncompliant
+----
+
+==== Compliant solution
+
+[source,python,diff-id=1,diff-type=compliant]
+----
+data = [3, 1, 4, 1, 5, 9]
+result = sorted(data, reverse=True)
+----
+
+== Resources
+=== Documentation
+- Python reference documentation - https://docs.python.org/3/library/functions.html#sorted[sorted]  
+- Python reference documentation - https://docs.python.org/3/library/functions.html#reversed[reversed]