fix: detect rule prefix from ConfigsToRules and apply to rule doc title

[y-hsgw]

This PR introduces a utility function detectPrefixFromConfigsToRules to infer the rule prefix by analyzing the rule IDs in ConfigsToRules, instead of relying on package.json.name.

Motivation

Currently, there's no single agreed-upon source for determining a plugin's rule prefix. It's unclear whether the most reliable approach is:

• Reading from configs[configName].plugins
• Inspecting configs[configName].rules
• Or potentially something else entirely

So, as a first step, I've made a minimal change that applies this prefix detection only to the rule documentation title.

Future Scope

Depending on how the discussion evolves, I’m open to applying this logic more broadly across the codebase (e.g. for rule links, config listings, etc.).

If this approach is misaligned with expectations or future direction, I’m also totally fine with closing this PR.

Notes

• The prefix is inferred by matching suffixes of rule names in plugin.rules with rule IDs in ConfigsToRules.
• This change is scoped and safe, intended to address the issue described in Documentation not generated when package.json name prefix and Config name mismatch #610.

Looking forward to your feedback!

[bmish]

Sorry about the delay. I've been busy and haven't had a chance to look yet, but hope to look soon, appreciate your work here.

[veritem]

hey any update from maintainers?