less code, no extension loading in <clinit>

in case an exception occurs when adding listener and instantiating extensions

to avoid calling it in run configuration actions (very expensive: PY-32762) but not disabling potentially enabled groups

This reverts commit 1a9d6609

relates to IDEA-102757

relates to IDEA-102757

new registry key: ide.find.use.editor.font=false

reset action text only if it's non-null: it'll overwrite the default suggestion which is too generics if there are several applicable run configurations

IDEA-202380 Can't assign non-array value to an array in Expression Evaluation window - better fix, not for 183

PY-24191 Skip sending superfluous messages from debugger to IDE about substituting current process with non-Python ones

PY-24191 Use explicit integer values for CommunicationRole constants, move CommunicationRole to pydevd_comm.py

Python documentation states about `os.exec*()` functions: "These functions all execute a new program, replacing the current process." This also applies for `subprocess.Popen()` in Python 2.x because it initially uses `os.fork()` and then `os.exec*()` function call for the child process.

Previously we put `CMD_PROCESS_CREATED` message in the queue and performed the original `os.exec*()` function call immediately. In the most cases Python debugger did not have enough time to process `CMD_PROCESS_CREATED` message from the queue and it has not being sent to the IDE.

Now when `PyDB` works in server mode we also wait for the response from the IDE after sending `CMD_PROCESS_CREATED` message to be sure that the IDE received it. Waiting for the response in server mode is required because the current process might become substituted before it actually sends the message and IDE will not try to connect to `PyDB` in this case. Waiting of the response in client mode is not required because the substituted process will try to connect to the IDE itself.