Integrations privileges can be lower or equal to Fleet-server service token privileges.
Today, if you specify privileges that are out of this boundaries it is simply ignored and lead to a confusion for integrations developers.

When creating and/or pushing a new packages we should verify those privileges and through and error if they are not included in fleet-server service token privileges.

Related:

elastic/fleet-server#1048

cc @ruflin