Which Cryptographic Standard ensures cryptographic agility and good adapotion Which Cryptographic Message Standards are recommended to ensure cryptographic agility in the future and good adapotion trough different programming languages (.NET and Go)?
(PublicKey with authenticated symetric encryption)
I doesn't want handle to cryptographic primitives myself, but rather I want to handle facade which protects more or less from small mistakes.
I found these different Standards, in which my experience varies:

PKCS #7 (Old standard, suitable for the future?)
NaCl crypto_box (Fixed primitives and limited message size)
JSON Web Encryption (JWE) (JWS is very well established, but not JWE)
XML Encryption Syntax and Processing Version 1.1 (Large overhead trough use of XML)

Are some worth mentioning missing? Which would be recommend for a future proof application?
Update
Application: is local installed and sends encrypted data over HTTPS with TLS Auth. to a service in the cloud, but data will be encrypted locally on-prem and not in cloud. One message is around 5kb-2MB and around 100-2.000 messeages per day. Crypt primitives should be fast, around ~50ms.
Constraints: Must be compatible with BSI TR-02102 and should be compatible with BSI recommendations (written in German) for the migration to post-quantum cryptography.
All but NaCl allow you to specify algorithms, but none of them would allow you to specify an algorithm that is part of the Post Quantum Cryptography initiatives yet (which, although unmentioned in the question, would be a very good reason to have crypto-agility).
For classic cryptography and a relatively high resistance against quantum computers, all those allow for RSA key encapsulation (including RSA-OAEP) and 256 bit AES as primitives. So using an RSA key pair of, say 4096 bits, will allow you to have a pretty good resistance against anything but a full featured quantum computer with more than 8192 logical qubits.
Otherwise I'd make sure that I would use a standard that is practical for you, that has a mature, well maintained library and is checked for e.g. side channel attacks. That's also something that's a good property of CMS; it may be old, but there is little wrong with maturity when it comes to choosing a library.