refactor: add wrapper around preg_match

[drupol]

Hi,

Description

The default behavior of preg_match is to silent any parsing error.
Therefore, I created a this wrapper is here to make sure that it properly throws an exception in case of any preg_match issue.

The origin of this PR comes from an issue we had at work. We were trying to delete a block in a .docx file (75Kb) and nothing was happening, despite the fact that the method issued correctly.
We made an introspection of the document.xml and discovered that the method TemplateProcessor::deleteBlock doesn't work, it seems that the regex is not valid (there are already a couple of issues about that: #2051, #2221, #2309, #2157), we are now using TemplateProcessor::cloneblock instead.
Then, we narrowed down the issue to the preg_match function and succeeded to reproduce the issue with a simple xml document.
This is were I discovered the function preg_last_error and noticed that the issue was related to the pcre.backtrack_limit PHP directive. Once we updated that directive from 1000000 to 2000000 it worked.

We lost less or more half a day on this issue, and this PR should help some people to see clearer when something goes wrong.

Could you please let me know if this PR is legit and if I should invest more time in it?

Nice to have: ideally, it would be a good think to invest time into an external contrib library that does preg_match correctly with the proper Exception handling.

Thanks

Checklist:

• I have run composer run-script check --timeout=0 and no errors were reported
• The new code is covered by unit tests (check build/coverage for coverage report)
• I have updated the documentation to describe the changes

[drupol]

Closing this PR since no feedback after 3 months.

[kovalovme]

BUMP