Add minimal template

[brophdawg11]

This is a slimmed down "minimal" template for create-react-router intended not as a production ready solution but a way to easily play with the framework, experiment, create demos, etc.

For now, this can be invoked via the --template flag but I think we may consider making it the default as well. My hunch is that the majority of create-react-router executions don't actually result in a production app or a deployment beyond localhost. Users who want that extra complexity can opt into it via --template.

This starts with the default template and removes the following:

• styling (tailwind, postcss, autoprefixer, app.css)
• docker setup (3 dockerfiles and dockerignore)
• <Welcome> component and associated images in favor of a simple home.tsx with a loader and a "Hello World" type component
• entry.server/entry.client files
  • The first thing I always do when creating a demo is remove these so there's less files to deal with. It is a bit of "magic" through and we've gone back and forth a few times in the past as to whether or not to include them so I don't feel too strongly about keeping them out

[brophdawg11]

We may want to beef this up with a link to the docs or something simple

[brophdawg11]

Because this is not marketed as production ready and the README doesn't even mention build/start I removed the NODE_ENV stuff here and the cross-env dependency. We can add it back in through if folks feel strongly

[brookslybrand]

I definitely like how simple this is, however, as is I don't think this should be the default.

We intentionally revamped our templates to be a little prettier. This would be a step backwards to remove it completely.

I get that having tailwind as a default for some is more config than necessary. I think with v4 coming so soon this will get even less cumbersome, since tw will simply be a Vite plugin.

I also think that for most people, tailwind is a reasonable default if they're just getting started, rapid prototyping, or using the template for teaching. If you remove it it ends up meaning for the majority of people they're going to have an added step of adding it back. Again, I think removing it would be a step backwards if this were the default

I'm all for removing the Dockerfile for the default experience, and saying "if you want to learn how to deploy your app, checkout all these ready to deploy options/read this doc that we have"