fix: [#1431] Dispatch the hidePlayButton on the Button Event to prevent that keep on the screen on some situations [#1431]

[catrielmuller]

Hi @kamranayub , I'm tried to reproduce the issue [#1431] that was resolved on the commit ( c5d710a )
So I created a Story to test this on different situations, I notices that if you use something like this

heart.on('pointerdown', async (_evnt: ex.Input.PointerEvent) => {
      if (!game.isPaused()) {
        game.stop();
        await loader.showPlayButton();
        game.start();
      }
    });

to implement a play/pause functionality, the showPlayButton show the button, however you need hide manually after the user click them again, to prevent that I recomend move that logic inside of the ShowPlayButton click event definition.

Also I added a Options property to the withEngine util to override the default engine options used by the all Stories.

===:clipboard: PR Checklist :clipboard:===

• 📌 issue exists in github for these changes
• 🔬 existing tests still pass
• 🙈 code conforms to the style guide
• 📐 new tests written and passing / old tests updated with new scenario(s)
• 📄 changelog entry added (or not needed)

==================

Closes #1431

Changes:

• withEngine utils support an aditional options parameter to override the Engine default options.
• Story to show a play / pause implementation.
• Dispatch the hidePlayButton on the Button Event to prevent that keep on the screen on some situations [Play button is not cleaned up on stop #1431].

[eonarheim]

👍

[eonarheim]

👍

[eonarheim]

@catrielmuller Thanks again! I like pause/start example in the story, definitely something we might port into documentation around pause/play