LDAP unable to handle large response

### Current Behavior

DependencyTrack does not manage large LDAP responses properly, neither is it able to have separate search queries for users and groups. Thus, users are not mapped appropriately and new users do not belong to any teams and therefore must be mapped manually.

This message is shown in the log:
```
2023-02-15 14:11:49,854 WARN [LdapConnectionWrapper] Partial results returned. If this is an Active Directory server, try using port 3268 or 3269 in LDAP_SERVER_URL
```

### Steps to Reproduce

1. Enable LDAP and receive receive a large response

### Expected Behavior

DT is able to handle large responses or it should have separate search queries for users and groups.

### Dependency-Track Version

4.7.0

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

_No response_

### Browser

Mozilla Firefox

### Checklist

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported

Start with LdapConnectionWrapper, named in the warning, and trace LDAP searches and user-to-team mapping. Reproduce the partial-results warning with a large LDAP response; the issue supplies no concrete response size or test fixture. Clarify whether large-response handling or separate user/group queries is intended. Done means affected users map to the expected teams without manual intervention.

Written by the indexing model from the issue text.