[ENHANCEMENT] Avoid GitHub action failure due to broken pnpm-lock.yaml

I noticed a few errors occurred in the GitHub Actions because the pnpm-lock.yaml file was broken. This may have happened due to merges of different branches while both updated the lockfile.

There are two consequences that emerge from this:

1. Broken pnpm-lock.yaml on master
2. GitHub action fails and components are not published

In order to fix #2, we can add the --fix-lockfile tag to avoid the action failure.

For #1, I think the lockfile would eventually be corrected after some merges, but we may think of a way to automatically update and commit after (or before) merging with master.

[andrewjschuang]

Could we also run pnpm install with the --fix-lockfile option in the pre-push/post-merge git hooks so the lockfile is automatically fixed when master is merged into a branch?

Yep, done

[js07]

Could we also run pnpm install with the --fix-lockfile option in the pre-push/post-merge git hooks so the lockfile is automatically fixed when master is merged into a branch?