[jamf_protect] Mark sensitive values as secret

[taylor-swanson]

There are two configuration values flagged in #8610 that need to be marked as secret (or not a secret if it doesn't contain a sensitive value):

• http_endpoint.secret_header
• http_endpoint.secret_value

In order to support secrets variables and validation, the package-spec version of the integration will need to be raised to 3.0.2 or higher. As a note, migrating to package-spec 3.0 or higher will more than likely trigger validation errors for fields.

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)