Migrate to @xterm org on npm

[Tyriar]

In order to prevent problems like #4857 in the future let's move to scoped packages on npm. I don't consider this a breaking change as it needs a manual action to update anyway.

Plan:

• Start publishing beta builds to @xterm/xterm, @xterm/addon-search, etc.
• Publish 5.4 to new scope
• Deprecate old packages with a message redirecting users to the new package name
• update all docs snippets including paths in <script> elements here and on xtermjs.org (added by @jerch)

[jerch]

@Tyriar Wow, that already created quite a refactoring noise. Thx for getting it fixed this quickly.

[Tyriar]

@jerch np, it was our tech debt week so conveniently timed 🙂 ended up being a pretty chunky VS Code PR too microsoft/vscode#197167

[davidfiala]

Would you please clarify how you are publishing the 5.4.0 betas during this transitional moment?

For example:

• 10 days ago: https://www.npmjs.com/package/@xterm/xterm/v/5.4.0-beta.14
• 18 days ago: https://www.npmjs.com/package/xterm/v/5.4.0-beta.37

For example: the timestamps indicate a more recent beta 14 publish than one numbered beta 37.

I could have figured it out myself, but I didn't see git tags on the betas, so I'm not sure if there is an easy way for an outsider to track which hash each beta corresponds to. Let me know if I missed something.

Thanks!

[Tyriar]

@davidfiala @xterm/xterm@beta is the new latest after this change went in. There isn't a stable yet but it will be 5.4.0 when it happens. The only way to check what commit the builds are based on currently it to look at the action log https://github.com/xtermjs/xterm.js/actions/workflows/release.yml

[jerch]

What might be confusing here, is the fact that the 14 is actually newer than the 37. Have not looked up the publish script - my guess is, that the script simply started over for the @xterm/xterm.

Which means - anything in @xterm/xterm in newer than the last beta release under just xterm.

[Tyriar]

I deprecated xterm and xterm-headless. I don't think I can give it a custom message unfortunately