Ticket 47573: schema push can be erronously prevented

Bug Description:
	 With the ticket https://fedorahosted.org/389/ticket/47490, the schema is not pushed if the consumer schema is
	a superset of the supplier schema.

	To determine that a schema is a superset, for each objectclass, the required attributes on the supplier are compared
	with the 'required' attribute on the consumer.  Same thing for the 'may' attributes.

	If we have an attribute that is moved on the supplier, from the 'MUST' list to the 'MAY' list.
	The supplier objectclass is a superset of the consumer objectclass, but will be evaluated to be subset => prevent schema push

Fix Description:
	When looking at each consumer OC, if a 'required' attribute in missing in the related supplier OC it checks
	if the attribute is present in the 'allowed' attribute in the related supplier OC.
	If it is, that means the attribure was moved from 'MUST' to 'MAY' in the new supplier schema and that any
	existing entry with that OC, will conform the new supplier schema

https://fedorahosted.org/389/ticket/47573

Reviewed by: Rich Megginson

Platforms tested: F17/F19(jenkins)

Flag Day: no

Doc impact: no
Ticket #47693 - Environment variables are not passed when DS is started via service

Description: Environment variables (except TERM and LANG) are ignored
if a program is started via service.

If it is started with systemctl, it takes this COMMAND and the values
are correctly passed to the server.
systemctl set-environment SLAPD_MXFAST=0 MALLOC_TRIM_THRESHOLD_=4096

To control them explicitly and to provide the same instructions to
the service and systemctl, it'd be good to have some variables
(SLAPD_MXFAST, MALLOC_TRIM_THRESHOLD_ and MALLOC_MMAP_THRESHOLD_ in
this patch) configurable.

https://fedorahosted.org/389/ticket/47693

Reviewed by rmeggins@redhat.com (Thank you, Rich!!)