[TESTS] Posible fix for multiple minor issues (- WIP #46 & #49 -)

Changes in file .codecov.yml:
 removeed `setup.py` from coverage quota

Changes in file .coveragerc:
 removeed `setup.py` from coverage quota

Changes in file .github/labeler.yml:
 added license to github label patterns

Changes in file .github/workflows/Tests.yml:
 just a version update

Changes in file README.md:
 improved spacing a little

REMOVED file tests/check_codecov_regression

.codecov.yml

@@ -57,7 +57,6 @@ flags:
   multicast:
     paths:
       - "multicast/"
-      - "!tests/"
   tests:
     paths:
       - "tests/"

.coveragerc

@@ -4,7 +4,7 @@ parallel = True
 sigterm = True
 
 [report]
-include = multicast/*,tests/*,setup.py
+include = multicast/*,tests/*
 # Regexes for lines to exclude from consideration
 exclude_lines =
     # Have to re-enable the standard pragma

.github/labeler.yml

@@ -44,3 +44,5 @@ Github:
   - .github/**/*
   - .github/*
   - README.md
+  - LICENCE
+  - LICENCE.md

.github/workflows/Tests.yml

@@ -435,8 +435,8 @@ jobs:
         hash -p ./.github/tool_shlock_helper.sh shlock ;
         ./tests/check_integration_coverage || echo "::warning file=tests/check_integration_coverage,line=1,endLine=1,title=SKIPPED::SKIP Integration Tests." ;
       shell: bash
-    - name: Upload Python ${{ matrix.python-version }} coverage to Codecov
-      uses: codecov/codecov-action@v3
+    - name: Upload Python ${{ matrix.python-version }} integration coverage to Codecov
+      uses: codecov/codecov-action@v4
       with:
         token: ${{ secrets.CODECOV_TOKEN }}
         files: ./test-reports/coverage_supplement.xml

README.md

@@ -140,16 +140,22 @@ p.join() # if not already handled don't forget to join the process and other ove
 #### Python function return code meanings
 
 `0` is the default and implies *success*, and means the process has essentially (or actually) returned nothing (or `None`)
+
 `1` is used when a *single* result is returned (caveat: functions may return a single `tuple` instead of `None` to indicate exit code `1` by returning a `boolean` success value, and result (which may also be encapsulated as an iteratable if needed) )
+
 `2` is used to indicate a *value and reason* are returned (caveat: functions may return a single `tuple` with a single value and reason and the value can be a `tuple`)
+
 `-1` is used to mean *many* of unspecified length and otherwise functions as `1`
 
 #### CLI exit code meanings
 
 `0` *success*
+
 `1` *none-sucsess* - and is often accompanied by warnings or errors
+
 `2 >` *failure* of specific reason
 
+
 #### Everything Else
 _(extra exit code meanings)_