[WIP] pywrapper - custom source terms for all solvers

[bigfooted]

Proposed Changes

Introduce custom source terms for all solvers through the python wrapper.

• reproduces the laminar buoyancy driven cavity testcase
• can simulate a turbulent premixed flame using turbulent flamespeed closure (TFC)

PR Checklist

Put an X by all that apply. You can fill this out after submitting the PR. If you have any questions, don't hesitate to ask! We want to help. These are a guide for you to know what the reviewers will be looking for in your contribution.

• I am submitting my contribution to the develop branch.
• My contribution generates no new compiler warnings (try with --warnlevel=3 when using meson).
• My contribution is commented and consistent with SU2 style (https://su2code.github.io/docs_v7/Style-Guide/).
• I used the pre-commit hook to prevent dirty commits and used pre-commit run --all to format old commits.
• I have added a test case that demonstrates my contribution, if necessary.
• I have updated appropriate documentation (Tutorials, Docs Page, config_template.cpp), if necessary.

To fix the issue, we should remove the assignment to index_Vel entirely, as it is not used anywhere in the code. This will eliminate the unused variable and make the code cleaner. Since the right-hand side of the assignment (varindex.get("VELOCITY_X")) does not have any side effects, it is safe to remove the entire line.

---

To fix the issue, we should remove the assignment to the unused variable primindex on line 103. Since the variable is not used anywhere in the function, its removal will not affect the functionality of the code. Care should be taken to ensure that the removal does not inadvertently delete any other necessary code or comments.

---

To fix the issue, we need to address the unused variable varindex. Since the variable is not used after its assignment, we can safely remove the assignment on line 212. This ensures that the code remains clean and avoids unnecessary computations.

If the variable was intended for documentation purposes or debugging, we could rename it to follow conventions for unused variables (e.g., _unused_varindex). However, there is no evidence in the code to suggest this intention.

---

To resolve the issue, we need to either remove the commented-out code or reinstate it as active code. Since there is no context indicating that the commented-out line is necessary or relevant, the best approach is to remove it entirely. This will improve code readability and eliminate potential confusion for developers.

---

To resolve the issue, the commented-out code on line 1354 should be removed. This ensures that the codebase remains clean and avoids confusion for developers. Removing the line does not affect functionality because the uncommented version of the code (line 1355) already serves the intended purpose.

Steps to implement the fix:

1. Locate the commented-out code on line 1354 in the file Common/include/CConfig.hpp.
2. Remove the line entirely.
3. Verify that the removal does not affect the functionality of the surrounding code.

---

To fix the issue, we need to either remove the commented-out code or reinstate it as active code if it is still relevant. Since there is no context suggesting that the function is required, the best course of action is to remove the commented-out line entirely. This will improve code readability and maintainability.

---

To resolve the issue, we will remove the commented-out code entirely. This approach is appropriate because the surrounding comments and cout statements indicate that bounds checking for species-related quantities is no longer performed. If this functionality is needed in the future, it can be reintroduced with proper testing and integration.

Steps to fix:

1. Remove the commented-out code block starting from line 5644 to line 5660.
2. Ensure that the removal does not affect the functionality of the remaining code.

---

To fix the issue, we should either remove the commented-out code entirely or reinstate it if it is still relevant. In this case, since the function CConfig::GetWall_SpeciesType is already implemented in the following lines (9163–9167), the commented-out version of the function is redundant and should be removed. This will improve code readability and maintainability.

The best way to fix this issue is to either remove the commented-out code entirely if it is no longer needed or reinstate it if it is still relevant and should be part of the active codebase. In this case, the commented-out code appears to be an incomplete switch statement for handling different wall species types. Since there is no indication that this code is actively being used or maintained, it is better to remove it to avoid confusion.

To fix the issue, we will remove the assignment to the unused variable primindex on line 103. Since the variable is not used anywhere in the function or the provided code, its removal will not affect the functionality of the program. This change will make the code cleaner and eliminate the CodeQL warning.

---

To fix the issue, we should remove the unused assignment to varindex on line 212. This will eliminate the redundant code and make the program cleaner and easier to maintain. Since the variable varindex is not used after this assignment, removing it will not impact the program's behavior.

---