Closes #3: Ignore random errors in certain cases

[jeawhanlee]

Description

Fixes #3
Introduces exclusions of known WP Rocket related errors in debug.log

Type of change

• Enhancement (non-breaking change which improves an existing functionality).

Detailed scenario

Errors Identified here will be flagged in e2e with develop branch

Technical description

Documentation

Added an exclusion for known wpr related errors, gather all wpr related errors and filter based on matches, also new patterns can be added using filters.

Patterns used:

'wp-rocket/inc/Dependencies/Database',
'WP_Rocket(.*)Table->create',
'wp-rocket/inc/Engine/Common/Database/Queries/AbstractQuery',
'Failed opening(.*?)wp-rocket/',

New dependencies

N/A

Risks

New type of errors with patterns not already covered could surface, that's the reason the option for a filter is available to still work till new pattern is implemented.

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.

Unticked items justification

• No test suite setup for this repo
• No entry points to protect
• No user error to handle