Add optional --ldap-max-search-depth to fix issue #601

[sneal]

Added an optional --ldap-max-search-depth flag to use with Operations Manager 3.0+. The new flag can be used like so:

om configure-ldap-authentication \
  --decryption-passphrase='supersecret' \
  --email-attribute='email' \
  --group-search-base='ou=Groups,dc=vmware,dc=com' \
  --group-search-filter='Corp' \
  --ldap-password='supersecret' \
  --ldap-rbac-admin-group-name='Admins' \
  --ldap-referrals=follow \
  --ldap-username=ldapadmin \
  --ldap-max-search-depth=5 \
  --server-ssl-cert="$(cat ~/ldap.crt)" \
  --server-url='ldaps://ad.vmware.com' \
  --user-search-base='Users' \
  --user-search-filter='devs' \
  --skip-create-bosh-admin-client \
  --precreated-client-secret='supersecret'

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[rhall-pivotal]

Pulled in the changes and rebased on main. Tests ran locally without issue. Merging!