Feature Request: Save/match login URLs at the TLD level

Context:
Currently, when saving a login through a browser extension (macOS Chrome, iOS Safari), 1Password automatically includes the full path and parameters (https://app.domain.com/signup?key=value).

This leads to mismatches when the same credentials are saved on a very specific subdomain, but used across multiple subdomains and/or paths (e.g., https://app.domain.com/app/ or https://domain.com).

Use case:
- Websites with different paths for signup and login.

Main benefit:
- Faster autofill across different app states without needing to manually edit each and every login after saving. 

Request:
Please provide an option that allows saved login URLs to default to domain-only.
Alternatively, allow us to disable path matching and fall back to origin-based matching only.

This would reduce friction for users working across multiple interfaces on the same domain and prevent save/edit loops.