Docs: mark methods and products that don't work in Node

[hsubox76]

We want to get rid of the "Node.js (Client)" sidebar entry in the reference docs and have one unified entry each for modular (the entry called "Javascript - modular") and compat (the entry called ("Javascript - compat (namespaced)"). Modular already did not have a separate entry for Node.

The only difference between the namespaced "JavaScript - compat" and namespaced "Node" docs were that the "Node" docs had some methods and products removed, as they don't work in Node.

This PR adds sentences on each product and method that doesn't work in Node, allowing us to use one set of docs for both "browser" and "Node" users (and any other environments).

The content changes are:

• Added sentences to the index page of each product that doesn't work in Node (Analytics, Messaging, Performance, Remote Config, Installations) and an explanation of the narrow circumstances where you can use App Check in Node.
• Added sentences to Auth and Firestore methods/classes/properties that don't work in Node.
• There was a change a while ago that forgot to add StorageErrorCode to the compat TOC, I did that.

Script changes are:

• I removed all the script stuff relating to Node docgen option (this is all in the directory scripts/docgen-compat)

Some tips for parsing:

• Anything with a packageDocumentation tag is text that appears at the top of a product's main index page
• Every (content) file change here is for the modular docs except packages/firebase/compat/index.d.ts which is the sole source of truth for compat docs. That file already had non-Node APIs marked with a @webonly tag which allowed the documentation tool to filter them out when creating the separate Node docs. I replaced those tags with text that will be visible in the reference docs.
• @remarks tag means that everything after it is excluded from table of contents entries, to save space, but appears in the full description of the item itself.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a7124e2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[google-oss-bot]

Size Report ¹

Affected Products

No changes between base commit (8421ba1) and merge commit (b0ef014).

Test Logs

• Base (8421ba1): https://github.com/firebase/firebase-js-sdk/actions/runs/5018414492
• Merge (b0ef014): https://github.com/firebase/firebase-js-sdk/actions/runs/5049318689

1. https://storage.googleapis.com/firebase-sdk-metric-reports/QfLFnO9kjv.html

[google-oss-bot]

Size Analysis Report ¹

Affected Products

No changes between base commit (8421ba1) and merge commit (b0ef014).

Test Logs

• Base (8421ba1): https://github.com/firebase/firebase-js-sdk/actions/runs/5018414492
• Merge (b0ef014): https://github.com/firebase/firebase-js-sdk/actions/runs/5049318689

1. https://storage.googleapis.com/firebase-sdk-metric-reports/V7Tul95LLj.html

[prameshj]

lgtm, except for one comment.

[egilmorez]

We also chatted about this offline, but added my observations here too. Thanks for sending this PR!

[MarkDuckworth]

I opened 7299 with additional changes for Firestore. But otherwise, Firestore looks good to me.

[dwyfrequency]

LGTM