fix(vue): canDismiss definition is now exposed

[liamdebeasi]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

• The canDismiss property was not auto generated on the ion-modal instance.
• This PR also updated the GitHub Actions workflows to ensure that all framework integration build results have been committed to the repo (to avoid this issue in the future).
  Note: I bumped the Node version on CI from 15.x to 16.x. There were some fixes in node 16 that caused package-lock files to be generated differently.

What is the new behavior?

• Added the canDismiss property to the modal vue wrapper

Does this introduce a breaking change?

• Yes
• No

Other information