fix(plugins): clarify recon plugin differentiation (closes #547)

[Ayushi-hi]

Related Issues

Closes #547

Type of Change

• Documentation update

Summary

Amass and Domain Finder previously shared nearly identical descriptions
and the same underlying command, making them indistinguishable in the
catalog. This PR fixes the metadata descriptions for all overlapping
recon plugins so contributors can immediately understand when to use
each one.

Plugins Updated

• amass — clarified as deep active attack-surface mapping
• domain-finder — clarified as root-domain discovery via intel mode
• subfinder — clarified as fast passive-only subdomain discovery
• dns_enum — clarified as DNS record enumeration (not subdomain discovery)
• dnsx — clarified as DNS resolver/validator, not a discovery tool

How Has This Been Tested?

• All JSON files validated and parse correctly
• No plugin functionality or binaries were modified
• Descriptions manually verified to be unique and non-interchangeable

Checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[Ayushi-hi]

The backend-unit and backend-integration failures are pre-existing
and not caused by this PR. They occur on main branch independently
of these changes and relate to http_inspector plugin resolution.

This PR only modifies metadata.json descriptions and checksums for
the recon plugins (amass, domain-finder, subfinder, dns_enum, dnsx)
as required by issue #547. No plugin logic was changed.

[utksh1]

Thanks for updating this. This is not ready yet: backend integration is failing, the PR has checksum/no-newline churn, and it changes domain-finder command behavior while the issue is about clarifying plugin differentiation. Please rebase, limit the diff to the metadata/docs clarification, refresh only the affected checksums, and get checks green.