Fix the search error after setting the ID in the title

[sy-records]

Summary

Fix the id set in the title, resulting in wrong link when searching.

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

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

If changing the UI of default theme, please provide the before/after screenshot:

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:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

• Chrome
• Firefox
• Safari
• Edge
• IE

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

• A convincing reason for adding this feature
• Related documents have been updated
• Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

---

• DO NOT include files inside lib directory.

[Koooooo-7]

After tests , the normal cases work fine. 👍
A little problem(maybe it is not a problem), when the id settings like :id=xxx%xxx ( including the %) , it will get this issues #1118 again.
cuz, at thegetAndRemoveConfig()

 .replace(/(?:^|\s):([\w-]+:?)=?([\w-%]+)?/g, (m, key, value) => {

we allowed the % for getting the resizing params , such as ':size=10%'.

this util relates to lots of configurations and makes things broken sometimes. 😅

At the same time, when the id config has some weird characters, this settings would broken also.
If possible, I glad to see this regex in getAndRemoveConfig() will be refined soon, or there would have better solution instead.

[sy-records]

The ':size=10%' of the image is unaffected.

Since I couldn't use local git commits directly, I changed one less place and now I can.

[Koooooo-7]

LGTM.:+1:

[anikethsaha]

@sy-records thanks for the PR. 💯

just a small point, we are using angular commit convention so the commit message format should match these guidelines.

[sy-records]

okey.