(ITS#4947) monitor schema should appear under subschema entry

[ahasenack@terra.com.br]

Full_Name: Andreas Hasenack
Version: 2.3.35
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (200.140.247.99)


(enhancement, or minor)

The monitor backend attributes and object classes, when loaded, should also be
exported in the subschema entries at the server.

I know of one ldap client that breaks because of this: luma. It says it can't
display the cn=monitor entries because it doesn't know the object classes or
attributes. I guess it uses this info to determine how to show each entry.