Make it easier to understand which debug configuration to pick when debugging a Python script

[meganrogge]

Testing microsoft/vscode-python#22081

It would be better if it could be assumed that the active file (with breakpoints) is what I'd like to debug

[luabud]

the problem is that if this is part of a e.g. Django app, we don't know if users want to debug it as a script or as part of the Django app. The key thing is that only the debug configurations are different for the scenarios listed in the drop down -- they could all end up debugging that active Python file (we've actually seen too many users get confused with selecting "Python file" when in fact they wanted a different configuration). I've wondered if replacing "Python file" with "Script" would make the decision making there less confusing, but not sure 🤔
@paulacamargo25 @cwebster-99 would love to hear your thoughts!

[cwebster-99]

I wonder if we could make this drop-down list smarter based on what we are able to gather about the user's project/environment? I am thinking in the case where the user is working on a Flask app, would we be able to tell based on their imports and filter out configurations that wouldn't resonate with their project. Not necessarily directly addressing this issue/suggestion but could be something to think about.

@luabud In the case of your example, I agree we should show the options as we don't know the users intentions. But, perhaps we could rename the selection to make it more clear. The first idea that came to mind was "Single Python File" or "Script" like you suggested.