Fix: processed-node-manager is created even in the environment that doesn't need a recorder

[YunFeng0817]

changes:

1. fix the issue: processed-node-manager is created even in the environment that doesn't need a recorder

In the built scripts, the new ProcessedNodeManager() statement is bundled into the global environment, which means it will be constructed whenever the script is loaded.
Currently, I'm trying to create a rrweb player page with the SSR (server-side render) and it doesn't have the RFA API on the server side. So it keeps throwing the error: requestAnimationFrame isn't defined.

2. solve ESLint errors introduced in feat: Ensure password inputs are masked when switching type #1170

[changeset-bot]

🦋 Changeset detected

Latest commit: 5f4bd8a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
rrweb	Patch
rrweb-snapshot	Patch
rrdom	Patch
rrdom-nodejs	Patch
rrweb-player	Patch
@rrweb/types	Patch
@rrweb/web-extension	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Juice10]

This is great, one things I'm afraid of now we've moved it to the record function is that we might get multiple ProcessedNodeManager raf loops if someone stops recording, and starts again. I think we should add it to the list of handlers that get switched off once recording stops.