Examples - in-lining data, fixing codesandbox

[kennedybaird]

Using examples/usecase-todo to change the examples approach to solve for codesandbox issues.

1. Moving to devcontainers as codesandbox is stopping supporting sandbox.config.json
2. Hardcoding seed data in the example, whilst keeping the seed-data command
3. Setting prisma to inherit versions
4. Removing postinstall to avoid possible conflicts with prisma minor patch changes to their generator

To solve for the examples snapshot tests:

• leaving the schema's in the example's folder
• adding a new test:monorepo-snapshot-test command to replace postinstall
• added a new test:examples-snapshot-tests to root package.json which targets the above command recursively in all examples folders
• added a new examples_snapshot_tests test to ci to run the above command once

This is going to significantly reduce the time for actions as each of the smoke tests currently runs the postinstall for all the examples each time (~5m).

This approach also allows us to handle framework-nextjs-two-servers as well.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit b23b849:

Sandbox	Source
@keystone-6/sandbox	Configuration

[dcousens]

Seed data - I think it's best if we just stop ignoring the example.db files

Honestly, I think this is a good approach. We do this already, and it's solid.

The primary downside I can see is the lack of human readability for the binary file on GitHub. We otherwise have the examples/script example to showcase data seeding.

[dcousens]

Maybe we can build the keystone.db files deterministically from our root scripts/ folder?

[kennedybaird]

Seed data - I think it's best if we just stop ignoring the example.db files

Honestly, I think this is a good approach. We do this already, and it's solid.

The primary downside I can see is the lack of human readability for the binary file on GitHub. We otherwise have the examples/script example to showcase data seeding.

The intention was to still have the needed seed-data files, but have the database seeded for the first run

[kennedybaird]

@dcousens - I think I've found a reasonable solution, have updated the PR.