Remove redundant subdomains from shared credentials

[Ronitsabhaya75]

Overall Checklist

• I agree to the project's Developer Certificate of Origin
• The top-level JSON objects are sorted alphabetically
• There are no open pull requests for the same update

for shared-credentials.json

• There's evidence the domains are currently related (SSL certificates, DNS entries, valid links between sites, legal documents etc.)
• If using shared, the new group serves login pages on each of the included domains, and those login pages accept accounts from the others. (For example, we wouldn't use a shared association from google.co.il to google.com, because google.co.il redirects to accounts.google.com for sign in.)
• If using from and to, the new group, the from domain(s) redirect to the to domain to log in.

Description of Changes

This PR removes several subdomains from shared-credentials.json that are redundant because their parent domains are already present in the exact same credential group.

Since password manager resources automatically include subdomains when a parent domain is matched, explicitly listing these subdomains alongside their parents is unnecessary.

The removed subdomains are:

• login.workflowmanager.app (covered by workflowmanager.app)
• community.pioneerdj.com (covered by pioneerdj.com)
• hk.jobsdb.com, sg.jobsdb.com, th.jobsdb.com (covered by jobsdb.com)

No new groups were added; this is strictly an optimization/cleanup of the existing data structure.