Enable headers for SOAP and REST Web Service Notifications

The feature added in 2017 R2 was for authentication of the SOAP payload, not for managing headers within the payload.  PI remains unusable as a secure source of data for Maximo without it because you can't configure a MAXAUTH header. There's no way to configure headers for Notification Rules associated with a PI AF Services v2017 SP1 Elements with a SOAP or REST Web Service Endpoint.  Authenticated web services, such as our company's Maximo's meter data inbound service requires a MAXAUTH header with a base64-encrypted username:password string.  As a result, you can't use PI as a source of data for Maximo's condition-based maintenance triggers and automated asset meter reading updates, if Maximo uses authentication on its web services.  That's a fairly common scenario with a high rate of return on the PI-Maximo integration efforts for a lot of customers.