Consider upgrading the default Browserless service from V1 to V2

### What feature is it?

Hi, I noticed that the current Docker Compose configuration still uses `browserless/chrome`, which is Browserless V1, while Browserless V2 is now available and actively maintained.

May I ask whether RSSHub is intentionally staying on V1 for compatibility reasons, or whether migrating to V2 simply has not been considered or prioritized yet?

### What problem does this feature solve?

On one of my RSSHub deployments, Browserless V1 consumes a noticeable amount of memory.

Browserless V2 may provide better resource efficiency and could potentially reduce memory usage for many self-hosted RSSHub users. It also benefits from ongoing maintenance, newer browser versions, and better long-term compatibility.

I understand that V2 may not be a drop-in replacement and that its actual memory usage would need to be tested with RSSHub workloads.

Would the maintainers consider evaluating Browserless V2 and, if it is compatible, updating the default Docker Compose configuration and documentation?

If staying on V1 is intentional, a brief note about the compatibility reason would also be very helpful. Thank you!

### Additional description

_No response_

### This is not a duplicated feature request or new RSS proposal

- [x] I have searched [existing issues](https://github.com/DIYgod/RSSHub/issues) to ensure this feature has not already been requested and this is not a [new RSS proposal](https://github.com/DIYgod/RSSHub/issues/new?assignees=&labels=RSS+proposal&template=rss_request_en.yml).

Start with the default Docker Compose configuration that uses browserless/chrome, then review the Browserless V2 compatibility and test it against RSSHub workloads. Done means either updating the default Docker Compose configuration and related documentation for a compatible V2 setup, or documenting why RSSHub must remain on V1.

Written by the indexing model from the issue text.