Move X.509 OIDs from crypto to X.509

[gilles-peskine-arm]

Move X.509 OID tables and functions from oid.c and oid.h in TF-PSA-Crypto, to a new module with no public interface in Mbed TLS.

Restore the functionality of MBEDTLS_X509_REMOVE_INFO which was removed in Mbed-TLS/TF-PSA-Crypto#143.

This is the X.509 part of the task (plus any prerequisite needed in crypto). Once X.509 no longer depends on crypto's OID module, follow up with Mbed-TLS/TF-PSA-Crypto#291.

[gilles-peskine-arm]

Strictly speaking, this is a product split task, not a 1.0/4.0 task. But since we're handling this as part of a work stream on the API redesign, I'm adding it to the 4.0 planning board.

[gilles-peskine-arm]

Investigation and prototyping in #10125 and Mbed-TLS/TF-PSA-Crypto#252 has shown that X.509 and crypto consume disjoint sets of functions from the OID module. The only overlap is in macros, where duplication doesn't really matter.

Hence the plan is to split oid.c and oid.h into two separate modules. X.509 will consume the part in the mbedtls repository and crypto will consume the part in crypto. Each half of the module will be associated with its corresponding unit tests. (There will be no new testing, just splitting what already exists.) To get there:

1. In mbedtls, restore the last version of *oid* before they were moved to the crypto submodule. Restore the OID module for use in X.509 #10166
2. In mbedtls, replay all relevant changes made in the crypto submodule.
3. In mbedtls, adapt the code and the build scripts to consume the copy in the mbedtls repository and stop consuming the copy in the crypto repository. This means a few tweaks to build scripts, include directives, compile-time guards, function names, etc.
4. In mbedtls, remove the parts that are not used.
5. In crypto, remove the parts that are not used directly.

Conveniently, 4+5 will result in not having any code duplication.