fix(props): consider prop types order for default bool value

[miro-ku]

Fix #7485

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[miro-ku]

Can i know, why there is no any action? Maybe i've made something wrong?

[posva]

Hey sorry for the delay, it went under my radar 😄
Could you add a test, please?

[miro-ku]

@posva done ;)

[miro-ku]

Anyone alive there?

[mariolamacchia]

Hey there! Does this PR require more work to do? I'd love to have these changes deployed 🙂

[yyx990803]

Thanks for the PR, I will be doing final reviews/merging of outstanding PRs next week, please be patient.

[yyx990803]

Thanks again for the PR. There is an edge case not taken into account in this fix - that the Vue runtime might run in a different document from the app's code (see https://github.com/vuejs/vue/blob/dev/src/core/util/props.js#L178-L186)

I implemented a similar logic in 81e1e47 which fixes the original issue.