Default regex for dynamic PEPs and rules does not cover `except`/`finally` PEPs

[korydraughn]

The regex string that follows needs to be changed to "[^ ]*pep_[^ ]*_(pre|post|except|finally)".

irods_rule_engine_plugin_python/src/main.cpp

Line 97 in 6a0af30

const std::string DYNAMIC_PEP_RULE_REGEX = "[^ ]*pep_[^ ]*_(pre|post)";

DYNAMIC_PEP_RULE_REGEX is used when the plugin_specific_configuration stanza in server_config.json does not explicitly define regexes_for_supported_peps. The code block below highlights where this occurs.

irods_rule_engine_plugin_python/src/main.cpp

Lines 466 to 475 in 6a0af30

	RuleExistsHelper::Instance()->registerRuleRegex(DYNAMIC_PEP_RULE_REGEX);
	// clang-format off
	log_re::debug({
	{"rule_engine_plugin", rule_engine_name},
	{"instance_name", _instance_name},
	{"log_message", "No regexes found in server_config for Python RE - using default regexes"},
	{"static_pep_rule_regex", STATIC_PEP_RULE_REGEX},
	{"dynamic_pep_rule_regex", DYNAMIC_PEP_RULE_REGEX},
	});

[trel]

We have discovered that DYNAMIC_PEP_RULE_REGEX is only used when the Python Rule Engine Plugin is the only language plugin installed and/or if the iRODS Rule Language Rule Engine Plugin has a startup issue (which should not happen) and this variable is then used as a fallback.

Regardless, we will be fixing DYNAMIC_PEP_RULE_REGEX here.