Fix compilation error when building OpenSSL 1.1.1q in MacOS 11+ for 3.9.15 and 3.8.15

[twangboy]

Make sure you have checked all steps below.

Prerequisite

• Please consider implementing the feature as a hook script or plugin as a first step.
  • pyenv has some powerful support for plugins and hook scripts. Please refer to Authoring plugins for details and try to implement it as a plugin if possible.
• Please consider contributing the patch upstream to rbenv, since we have borrowed most of the code from that project.
  • We occasionally import the changes from rbenv. In general, you can expect changes made in rbenv will be imported to pyenv too, eventually.
  • Generally speaking, we prefer not to make changes in the core in order to keep compatibility with rbenv.
• My PR addresses the following pyenv issue (if any)
  • Additional fixes for: python 3.11.0 fails to build on macOS (OpenSSL build failure) #2494

Description

• Here are some details about my PR
  Python updated openssl to version 1.1.1q in 3.8.15, 3.9.15 and 3.11. Python 3.10.7 is at 1.1.1o.
  The following PR added a patch for building openssl 1.1.1q on 3.11 but not for 3.8.15 and 3.9.15.
  Fix compilation error when building OpenSSL 1.1.1q in MacOS 11+ #2500
  This applies the openssl 1.1.1q patches to the 3.8.15 and 3.9.15 builds of python.

Tests

• My PR adds the following unit tests (if any)
  N/A

[native-api]

What's this?

[twangboy]

.idea is a directory created by pycharm
*.un~ is a lockfile created by vim

[amureki]

Extending project's .gitignore with personal OS/tooling-related files and paths is usually not recommended practice.
Especially in this exact case, it is totally unrelated to the patch you are providing.

I suggest you configuring global .gitignore file for your workstation:
https://adamj.eu/tech/2022/11/06/git-set-up-a-global-ignore-file/

[native-api]

I think IDEA/Pycharm and Vim are used widely enough to warrant adding.

It's okay to address additional concerns in a PR (as long as it's within reason, of course), but then each concern needs to be in its own commit (see the contribution giude).

[native-api]

@twangboy Could you please restructure the commits as per the contribution giude, or move the gitignore part to another PR?