feat: deprecate all functions & types exported from magicExports

[MichaelDeBoey]

I wanted to re-submit #2735 again, as:

• The first release supporting separate packages was 1.3.3, which was released on 23 Mar 2022
  https://github.com/remix-run/remix/releases/tag/v1.3.3
• The replace-remix-imports migration was added in 1.4.0, which was released on 14 Apr 2022
  https://github.com/remix-run/remix/releases/tag/v1.4.0
• We now export functions/types that aren't available anymore through the remix package, as they're not included in the magicExports anymore (see both @remix-run/cloudflare & @remix-run/node) since 1.5.0
• We now have a runtime package (@remix-run/deno) that doesn't have any magic exports at all since 1.5.0
  https://github.com/remix-run/remix/releases/tag/v1.5.0
• Our ESLint config is warning with a deprecated message when importing from the remix package since 1.6.0
  https://github.com/remix-run/remix/releases/tag/v1.6.0

---

Original PR description:

As a follow-up of #2731, this will show deprecation warnings in the IDE + in console whenever people aren't using the ESLint config.

Inspired by @pcattori's remark (#2542 (comment)) on @mjackson's PR to rename createCloudflareKVSessionStorage to createWorkersKVSessionStorage (#2542).

Since each package is on it's own, I had to copy/paste the warn & getDeprecatedMessage functions over to each package.

If this somehow could be simplified (as this is doing the same thing over & over again), I'd be happy to do so.

[kentcdodds]

I want @mjackson or @ryanflorence to approve this before merging.

[MichaelDeBoey]

@mjackson @ryanflorence Our ESLint config is warning with a deprecated message when importing from the remix package since 1.6.0, so I think we can merge this one as well now?
https://github.com/remix-run/remix/releases/tag/v1.6.0

[mjackson]

I think now is a great time to officially deprecate using magic exports 👍

Do you know why the tests are failing in the diff view @MichaelDeBoey? Is that something to do with this PR? Or just something that has been happening for a while now? I'd like to clean that up if we can. If the test failures are unrelated to this PR, it's a huge distraction.

Can you also please say more about the approach you're taking here? It looks like you're generating a bunch of code in the build output. Is that right? I think I'd prefer to just write out the code (it's repetitive, I know) instead of introduce more complexity in our build.

[MichaelDeBoey]

Do you know why the tests are failing in the diff view?

@mjackson If you're talking about the failing tests underneath Unchanged files with check annotations, this has been happening for a while now.

Can you also please say more about the approach you're taking here? It looks like you're generating a bunch of code in the build output. Is that right? I think I'd prefer to just write out the code (it's repetitive, I know) instead of introduce more complexity in our build.

In #3543, @chaance removed all manual magicExports files & replaced it by generating them.
The generation script is taking the defined functions/types from rollup.config.js's getMagicExports & creates these magicExports files we had before.

My changes are building upon that script, by wrapping all exported functions in a warn function that's console.warning a deprecation message before calling the actual function (just like we do in #2542).

My changes also add an /** @deprecated **/ typehint to all functions/types & points them towards using the actual packages instead of using 'remix' package.

[chaance]

@mjackson We moved to code generation here because having the code in the workspace was causing TypeScript issues when we did our Rollup build overhaul a while back. It was always intended to be temporary as we planned on removing the exports altogether, but we went this route to move a little quicker, as that refactor was blocking other work (specifically, adopting Changesets as noted in #3543).

[chaance]

These look good overall. Can you merge the latest from dev one last time? Once that's taken care of I'll cut an experimental release to manually check the dev warnings, and if everything looks good we'll get this in for the next minor bump.

Thanks so much for seeing this through! 🙏

[chaance]

@MichaelDeBoey Just FYI, the only reason I haven't merged this yet is because I want to time it with an upcoming minor release. Once @brophdawg11 and @jacob-ebey finalize their work integrating React Router 6.4 I'll merge this and ship them together.

Just wanted you to know so you don't need to keep resolving conflicts until we're there!

[chaance]

@MichaelDeBoey Ready to merge this if you're able to bring the branch up-to-date 😄

[MichaelDeBoey]

@chaance Rebase onto latest dev, so this should be OK to merge now 👍