Consider switching back to omniauth_ldap after merging our patches
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=580013)
</details>
<!--IssueSummary end-->
omniauth_ldap has become active again https://github.com/intridea/omniauth-ldap/issues/61#issuecomment-181526838
It would be a good idea to check if all gitlab-omniauth_ldap patches are send upstream and if not send new merge requests. Once all patches are merged, we can switch to using omniauth_ldap to avoid maintaining a fork.
@dzaporozhets @rspeicher
### Proposal
**Please see Drew's notes on the [testing needed]**(https://gitlab.com/gitlab-org/gitlab/-/merge_requests/213104#note_2955330351) before we proceed to adopt the upstream gem again
issue