Fix MarkBind internal package dependencies

[tlylt]

What is the purpose of this pull request?

• Documentation update
• Bug fix
• Feature addition or enhancement
• Code maintenance
• Others, please explain:

Overview of changes:
Fixes #1845

Anything you'd like to highlight / discuss:
Not sure if packages/core-web/package.json's dev dep on vue-components needs to be adjusted as well (may not be necessary).

Testing instructions:
nil

Proposed commit message: (wrap lines at 72 characters)
Ensure the referenced versions of MarkBind packages are exact

The use of range versions for internal packages results in
incorrect versioning of MarkBind packages when using an
older version of MarkBind.

Let's remove the compatible versioning and use the exact match.

This ensures the versions of internal packages downloaded
will be exact and provide the expected functionalities.

Checklist: ☑️

• Updated the documentation for feature additions and enhancements
• Added tests for bug fixes or features
• Linked all related issues
• No unrelated changes

[jonahtanjz]

Thanks @tlylt!

Not sure if packages/core-web/package.json's dev dep on vue-components needs to be adjusted as well (may not be necessary).

Don't think it's necessary but for consistency I think we should remove it as well.

Will also need to update the developer guide for doing a release. Usually these versions are incremented using the command lerna version --no-push (see step 2), which automatically adds in the ^. Will have to include the --exact option so that future releases will exclude the ^ as well.

[tlylt]

Will also need to update the developer guide for doing a release. Usually these versions are incremented using the command lerna version --no-push (see step 2), which automatically adds in the ^. Will have to include the --exact option so that future releases will exclude the ^ as well.

Updated accordingly here.

[jonahtanjz]

LGTM 👍