docs(linter): improve docs for node/security/tree_shaking rules

[shulaoda]

Related to #6050

As of this PR, all documents of that contain a few rules have been corrected.

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[codspeed-hq]

CodSpeed Performance Report

Merging #6097 will not alter performance

_{Comparing shulaoda:docs/node-security-tree_shaking (c5b7dc5) with main (418ae25)}

Summary

✅ 29 untouched benchmarks

[graphite-app]

Merge activity

• Sep 26, 11:54 PM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Sep 26, 11:54 PM EDT: camchenry added this pull request to the Graphite merge queue.
• Sep 26, 11:55 PM EDT: The Graphite merge queue couldn't merge this PR because it failed for an unknown reason.
• Sep 27, 2:28 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Sep 27, 2:28 AM EDT: Boshen added this pull request to the Graphite merge queue.
• Sep 27, 2:29 AM EDT: The Graphite merge queue couldn't merge this PR because it failed for an unknown reason (Stack merges are not currently supported for forked repositories. Please create a branch in the target repository in order to merge).