GH-155009: Preserve argparse prog for programmatic module-as-main execution

[savannahostrowski]

I opted to compare sys.argv[0] with __main__.__spec__.origin because looking for an adjacent -m, module pair in sys.orig_argv can mistake application arguments for an interpreter option and miss valid forms such as -mmodule.

• Issue: argparse reports python -m for programmatic module-as-main execution #155009

[miss-islington-app]

Thanks @savannahostrowski for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15.
🐍🍒⛏🤖

[bedevere-app]

GH-155200 is a backport of this pull request to the 3.15 branch.

[bedevere-app]

GH-155201 is a backport of this pull request to the 3.14 branch.

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot ARM64 Raspbian 3.14 (tier-3) has failed when building commit d9f94ee.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1764/builds/1409) and take a look at the build logs.
4. Check if the failure is related to this commit (d9f94ee) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1764/builds/1409

Failed tests:

• test_argparse

Failed subtests:

• test_module_as_main_without_altering_argv - test.test_argparse.TestProgName.test_module_as_main_without_altering_argv

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/test_argparse.py", line 7141, in test_module_as_main_without_altering_argv
    self.check_usage(os.path.basename(runner), runner,
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                     PYTHONPATH=os.curdir)
                     ^^^^^^^^^^^^^^^^^^^^^
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/test_argparse.py", line 7098, in check_usage
    res = script_helper.assert_python_ok('-Xutf8', *args, '-h', **kwargs)
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/support/script_helper.py", line 182, in assert_python_ok
    return _assert_python(True, *args, **env_vars)
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/support/script_helper.py", line 167, in _assert_python
    res.fail(cmd_line)
    ~~~~~~~~^^^^^^^^^^
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/support/script_helper.py", line 80, in fail
    raise AssertionError(f"Process return code is {exitcode}\n"
    ...<10 lines>...
                         f"---")
AssertionError: Process return code is 1
command line: ['/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/python', '-X', 'faulthandler', '-Xutf8', 'packageæ/runner.py', '-h']

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot ARM64 Raspbian 3.14 (tier-3) has failed when building commit d9f94ee.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1764/builds/1410) and take a look at the build logs.
4. Check if the failure is related to this commit (d9f94ee) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/1764/builds/1410

Failed tests:

• test_argparse

Failed subtests:

• test_module_as_main_without_altering_argv - test.test_argparse.TestProgName.test_module_as_main_without_altering_argv

Summary of the results of the build (if available):

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/test_argparse.py", line 7141, in test_module_as_main_without_altering_argv
    self.check_usage(os.path.basename(runner), runner,
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                     PYTHONPATH=os.curdir)
                     ^^^^^^^^^^^^^^^^^^^^^
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/test_argparse.py", line 7098, in check_usage
    res = script_helper.assert_python_ok('-Xutf8', *args, '-h', **kwargs)
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/support/script_helper.py", line 182, in assert_python_ok
    return _assert_python(True, *args, **env_vars)
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/support/script_helper.py", line 167, in _assert_python
    res.fail(cmd_line)
    ~~~~~~~~^^^^^^^^^^
  File "/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/Lib/test/support/script_helper.py", line 80, in fail
    raise AssertionError(f"Process return code is {exitcode}\n"
    ...<10 lines>...
                         f"---")
AssertionError: Process return code is 1
command line: ['/home/stan/buildarea/3.14.stan-raspbian.nondebug/build/python', '-X', 'faulthandler', '-Xutf8', 'packageæ/runner.py', '-h']