Feat(URL): Update url endpoints

[Guiliano99]

Add additional endpoints for the reaching the MockCA.

Description

• Add the prefixes /<pkibody_type>, /issuing/<pkibody_type>, /.well-known/cmp/p/<pkibody_type>
• Add new endpoints for the reaching the MockCA.
• As an example OpenSSL append the PKIBody type to the -server argument.
• Add new config variable ADD_PKIBODY_TYPE_2_URL to add the pkibody name to the url, if that config variable is set to True.

TODO

• Add additional test cases for testing, if only the correct PKIBody type is accepted for each URL.

Motivation and Context

• Some implementations uses the URL endpoints define in RFC9480 and RFC9810

How Has This Been Tested?

• Added new unit test for checking the unit test endpoint.
• Tested to run the test cases again against the MockCA with the ADD_PKIBODY_TYPE_2_URL variable set to True.

[ralienpp]

This looks OK but the naming could be better, because "type 2" is not an evident meaning. What is the essence of this thing? Add a suffix? Expand or augment the original URL? I'd rather use these keywords instead of "type 2".

[Guiliano99]

This looks OK but the naming could be better, because "type 2" is not an evident meaning. What is the essence of this thing? Add a suffix? Expand or augment the original URL? I'd rather use these keywords instead of "type 2".

It expands the original URL, with the PKIBody type names, like for genm it would be added like this http://127.0.0.1:5000/issuing/genm. i wanted to also add it in the config for easly updting the default url. Becasue OpenSSL does it. But some other implementation might not.

[Guiliano99]

@ralienpp I think you are right: What about APPEND_PKIBODY_AS_URL_SUFFIX?