chore(release): note breaking changes for v5

[mcous]

8d98aa5 landed in next with two issues that I didn't realize when I was writing my commit message:

• semantic-release uses the angular commit spec rather than the conventional commit spec, which means it did not recognize the exclamation mark in fix!: ... as a breaking change
• I typed BREAKING CHANGES: rather than BREAKING CHANGE: in the commit body

This means that the breaking changes in #325 were released improperly as v4.2.2 instead of v5.0.0 on the next dist tag. This PR adds an empty commit with the correct BREAKING CHANGE message below to hopefully trigger a major bump. I'm leaving this as a draft in case there are other breaking changes that should be incorporated in the v5 release.

BREAKING CHANGE: render is now more strict about the target option, and the container result is now the direct parent of your component instance.

[mcous]

@yanick looks like we just had another release go out on next, did you see this PR and my notes?

[yanick]

Yup, I am on this very page and was about to say "let's merge this, and get v5 out of the door".

So, uh, let's merge this, and get v5 out of the door. :-)

[github-actions[bot]]

:tada: This PR is included in version 5.0.0 :tada:

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[github-actions[bot]]

:tada: This PR is included in version 5.0.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: