Modernize linting and configuration setup

.github/DISCUSSION_TEMPLATE/installation.yml

@@ -1,20 +1,20 @@
---- 
-body: 
-  - 
-    attributes: 
+---
+body:
+  -
+    attributes:
       label: "What operating system are you using?"
     id: os
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       label: "How did you install slither?"
       description: |
         For example, using git or python's pip.
     id: install-method
     type: textarea
-    validations: 
+    validations:
       required: true
   - type: dropdown
     id: python
@@ -25,14 +25,14 @@ body:
         - "Yes"
         - "No"
         - "Not sure"
-  - 
-    attributes: 
+  -
+    attributes:
       description: |
-          Please copy and paste any relevant log output. This 
+          Please copy and paste any relevant log output. This
           will be automatically formatted into code, so no need for backticks.
       render: shell
       label: "Output of running `slither-doctor .`:"
     id: logs
-labels: 
+labels:
   - installation-help
 title: "[Installation-Help]: "

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,54 +1,54 @@
---- 
-body: 
-  - 
-    attributes: 
+---
+body:
+  -
+    attributes:
       value: |
-          Please check the issues tab to avoid duplicates, and 
+          Please check the issues tab to avoid duplicates, and
           confirm that the bug exists on the latest release (upgrade
           by running `python3 -m pip install --upgrade slither-analyzer`).
-          
+
           If you are having difficulty installing slither,
           please head over to the "Discussions" page.
-          
+
           Thanks for taking the time to fill out this bug report!
     type: markdown
-  - 
-    attributes: 
+  -
+    attributes:
       label: "Describe the issue:"
     id: what-happened
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: "It can be a github repo (preferred), etherscan link, or code snippet."
       label: "Code example to reproduce the issue:"
       placeholder: "`contract A {}`\n"
     id: reproduce
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: |
           What version of slither are you running?
           Run `slither --version`
       label: "Version:"
     id: version
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: |
-          Please copy and paste any relevant log output. This 
+          Please copy and paste any relevant log output. This
           will be automatically formatted into code, so no need for backticks.
       render: shell
       label: "Relevant log output:"
     id: logs
     type: textarea
 description: "File a bug report"
-labels: 
+labels:
   - bug-candidate
 name: "Bug Report"
 title: "[Bug-Candidate]: "

.github/ISSUE_TEMPLATE/false_negative.yml

@@ -1,61 +1,61 @@
---- 
-body: 
-  - 
-    attributes: 
+---
+body:
+  -
+    attributes:
       value: |
-          Please check the issues tab to avoid duplicates. 
+          Please check the issues tab to avoid duplicates.
           Thanks for helping make Slither the best it can be!
     type: markdown
-  - 
-    attributes: 
+  -
+    attributes:
       label: "What bug did Slither miss and which detector did you anticipate would catch it?"
     id: what-happened
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
+  -
     attributes:
       label: Frequency
       description: How often do you run across this false negative?
       options:
         - Very Frequently
-        - Occasionally 
+        - Occasionally
         - Rarely
         - Not sure
     id: frequency
     type: dropdown
     validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: "It can be a github repo, etherscan link, or code snippet."
       label: "Code example to reproduce the issue:"
       placeholder: "`contract A {}`\n"
     id: reproduce
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: |
-          What version of slither are you running? 
+          What version of slither are you running?
           Run `slither --version`
       label: "Version:"
     id: version
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: |
-          Please copy and paste the result output. This 
+          Please copy and paste the result output. This
           will be automatically formatted into code, so no need for backticks.
       render: shell
       label: "Relevant log output:"
     id: logs
     type: textarea
 description: "Slither missed a bug it should find."
-labels: 
+labels:
   - false-negative
 name: False Negative
 title: "[False Negative]: "

.github/ISSUE_TEMPLATE/false_positive.yml

@@ -1,61 +1,61 @@
---- 
-body: 
-  - 
-    attributes: 
+---
+body:
+  -
+    attributes:
       value: |
-          Please check the issues tab to avoid duplicates. 
+          Please check the issues tab to avoid duplicates.
           Thanks for helping make Slither the best it can be!
     type: markdown
-  - 
-    attributes: 
+  -
+    attributes:
       label: "Describe the false alarm that Slither raise and how you know it's inaccurate:"
     id: what-happened
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
+  -
     attributes:
       label: Frequency
       description: How often do you run across this false positive?
       options:
         - Very Frequently
-        - Occasionally 
+        - Occasionally
         - Rarely
         - Not sure
     id: frequency
     type: dropdown
     validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: "It can be a github repo, etherscan link, or code snippet."
       label: "Code example to reproduce the issue:"
       placeholder: "`contract A {}`\n"
     id: reproduce
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: |
-          What version of slither are you running? 
+          What version of slither are you running?
           Run `slither --version`
       label: "Version:"
     id: version
     type: textarea
-    validations: 
+    validations:
       required: true
-  - 
-    attributes: 
+  -
+    attributes:
       description: |
-          Please copy and paste the result output. This 
+          Please copy and paste the result output. This
           will be automatically formatted into code, so no need for backticks.
       render: shell
       label: "Relevant log output:"
     id: logs
     type: textarea
 description: "Slither warned of an issue that is not legitimate and does not need to be fixed."
-labels: 
+labels:
   - false-positive
 name: "False Positive"
 title: "[False-Positive]: "

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -14,4 +14,4 @@ body:
       label: Describe the desired feature
       description: Explain what the feature solves/ improves.
     validations:
-      required: true
+      required: true

.github/dependabot.yml

@@ -1,8 +1,8 @@
 ---
 version: 2
 updates:
-    - package-ecosystem: "github-actions"
-      directory: "/"
-      target-branch: "dev"
-      schedule:
-        interval: "weekly"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    target-branch: "dev"
+    schedule:
+      interval: "weekly"

.github/scripts/integration_test_runner.sh

@@ -1,13 +1,16 @@
 #!/usr/bin/env bash
 
+# Use UV_RUN if set (for CI), otherwise run directly (for local dev)
+RUN="${UV_RUN:-}"
+
 # used to pass --cov=$path and --cov-append to pytest
 if [ "$1" != "" ]; then
-    pytest "$1" tests/e2e/ -n auto
+    $RUN pytest "$1" tests/e2e/ -n auto
     status_code=$?
-    python -m coverage report
+    $RUN python -m coverage report
 else
-    pytest tests/e2e/ -n auto
+    $RUN pytest tests/e2e/ -n auto
     status_code=$?
 fi
 
-exit "$status_code"
+exit "$status_code"

.github/scripts/tool_test_runner.sh

@@ -1,13 +1,16 @@
 #!/usr/bin/env bash
 
+# Use UV_RUN if set (for CI), otherwise run directly (for local dev)
+RUN="${UV_RUN:-}"
+
 # used to pass --cov=$path and --cov-append to pytest
 if [ "$1" != "" ]; then
-    pytest "$1" tests/tools
+    $RUN pytest "$1" tests/tools
     status_code=$?
-    python -m coverage report
+    $RUN python -m coverage report
 else
-    pytest tests/tools
+    $RUN pytest tests/tools
     status_code=$?
 fi
 
-exit "$status_code"
+exit "$status_code"