Symbolic link on build_devtoolset.sh
I am unsure of what problem this is really solving.  This only executes in a docker container where these things are not changing. This seemingly complicates the script for little benefit.   Do you have an issue describing the problem this is causing?  Sorry, we're not looking for "generally better" changes for this script right now. If there's a very specific bug that you have encountered, please explicitly state and fix it. This commit right here was made with the intent of bettering the structure and build of the code. Here's are some key differences between the original version and my proposed one:

- The first code does not check for the existence of the Python interpreter or the symbolic link, while the second code does.
- The first code does not execute any Python code or handle any errors, while the second code does.
- The first code creates the directory unconditionally, while the second code creates it only if the Python interpreter is found.
- The first code uses a hard-coded array of Python versions, while the second code uses a variable that can be changed easily.

As you can see, my main objective wasn't trying to fix a bug, rather to increase the robustness of the code.
Commit that aims at bettering the overall symbolic link connection for python versions. I also included some error handling and it prints `"No suitable Python version found"` in case it doesn't find the correct Python version.