Chore: Document making the text icon bold with t-class in lists

[kaixin-hc]

What is the purpose of this pull request?

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

Addresses #2489

Overview of changes:
Adds an example of bold text to the customising text-icon for bold text section

Anything you'd like to highlight/discuss:
I don't think the look of it is great but I think this makes it visible for users.

Testing instructions:

Proposed commit message: (wrap lines at 72 characters)
Document bootstrap classes with t-class in lists

---

Checklist: ☑️

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

---

Reviewer checklist:

Indicate the SEMVER impact of the PR:

• Major (when you make incompatible API changes)
• Minor (when you add functionality in a backward compatible manner)
• Patch (when you make backward compatible bug fixes)

At the end of the review, please label the PR with the appropriate label: r.Major, r.Minor, r.Patch.

Breaking change release note preparation (if applicable):

• To be included in the release note for any feature that is made obsolete/breaking

Give a brief explanation note about:

• what was the old feature that was made obsolete
• any replacement feature (if any), and
• how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

[EltonGohJH]

I am okay with the change.
I think I could not tell that the text is bolded if I am not looking for it.

Are there any areas where the doc mention that you can use fw-bold to bold? If not we should mention it somewhere on the docs. Wdyt

[kaixin-hc]

You make a good point - I've added a tooltip that signposts to look at the bootstrap documentation, and also added italics to the one that is below so that the text having difference is more expected. See below picture

---

[EltonGohJH]

LGTM. Thanks for the change!

[github-actions]

@kaixin-hc Each PR must have a SEMVER impact label, please remember to label the PR properly.