feat: add configurable status code filtering for PageCache filter

[michalsn]

Description
This PR introduces a new configuration property, Config\Cache::$cacheStatusCodes, which allows developers to explicitly control which HTTP response status codes are cached.

This is important because not all responses should be cached by default. In practice, applications may want to cache responses beyond 200 OK (for example, 404), or the opposite - prevent caching of certain status codes to avoid serving stale or misleading responses. Making this configurable gives developers good control over cache behavior.

Minor BC break:
The PageCache filter constructor now accepts an optional Cache parameter to allow dependency injection (primarily for testing). This should not affect most users, as the parameter has a default value and existing usage continues to work unchanged.

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[datamweb]

Just a quick note: an empty array [] currently means cache all status codes, but it might read as cache nothing at first glance. Using something like [Cache::ALL_STATUS_CODES] or ['*'] could make it clearer.

[michalsn]

I considered it, but storing all status codes in one place seems counterproductive. Using ['*'] would also require a mixed property type, which could lead to confusion when users start declaring status codes as strings rather than integers. Since the behavior of an empty array is documented both in the config file and the user guide, this feels like the correct approach.

[datamweb]

but storing all status codes in one place seems counterproductive

I wasn’t suggesting enumerating all status codes.
My intent was a single sentinel value (e.g. a constant or numeric marker) that clearly communicates all statuses, while remaining type-safe.

public const ALL_STATUS_CODES = -1;

That said, I understand the preference to rely on documentation.

[michalsn]

Oh, okay - thanks for the clarification. If more users agree that having something like ALL_STATUS_CODES is preferable, then I'm happy to make the change.

[neznaika0]

I don't see the point in adding a constant. The empty array looks correct. In the future, we can update if receive a bug report.