Fix the squished piskel editor space bug

[jmkulwik]

Updates our repo to use code-dot-org/piskel#59 which fixes the squished piskel editor space bug. See that PR for details

Note: I'm noticing as I hand-test this for correctness, that our code-dot-org repo automatically overrides the default view so new piskel editors are always 100x100 pixels, effectively ignoring the "Default value" setting. It does this by rendering the default view and then immediately overwriting it with a 100x100 view, or whichever user-created image is first on the list. This can be traced by placing a breakpoint in the code where a new frame is created. This is called twice - once when the default view is rendered (where the error was being thrown) and once when the overwriting view is rendered.

We should consider whether we want to overwrite the default view even when there is no user-created image. However, that is a follow-up discussion. For now, pulling in the updates from the piskel repo is sufficient to fix the squished editor bug and prevent the user from getting into an unrecoverable state.

Links

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked