Add Parsec Basic Client

[tgonzalezorlandoarm]

Make the Parsec Provider context have a reference to an instance of a Parsec Basic Client. This client will be used for any operation requests coming from the Parsec Provider.

[tgonzalezorlandoarm]

Please see results of: https://github.com/parallaxsecond/parsec-openssl-provider/actions/runs/8006758451

[tgonzalezorlandoarm]

New relevant run: https://github.com/parallaxsecond/parsec-openssl-provider/actions/runs/8017305100

[tgonzalezorlandoarm]

New CI run : https://github.com/parallaxsecond/parsec-openssl-provider/actions/runs/8047902487

[tgonzalezorlandoarm]

https://github.com/parallaxsecond/parsec-openssl-provider/actions/runs/8139096688

[gowthamsk-arm]

The order of CI execution looks a bit strange to me

+ openssl version
OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
+ pushd /tmp/parsec
/tmp/parsec /tmp/parsec-openssl-provider
+ popd
/tmp/parsec-openssl-provider
+ wait_for_service
++ pgrep parsec
+ ./target/debug/parsec -c e2e_tests/provider_cfg/mbed-crypto/config.toml
+ '[' -z 8 ']'
+ sleep 5
+ pgrep parsec

this ./target/debug/parsec -c e2e_tests/provider_cfg/mbed-crypto/config.toml runs after wait_for_service??

[tgonzalezorlandoarm]

The order of CI execution looks a bit strange to me

+ openssl version
OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
+ pushd /tmp/parsec
/tmp/parsec /tmp/parsec-openssl-provider
+ popd
/tmp/parsec-openssl-provider
+ wait_for_service
++ pgrep parsec
+ ./target/debug/parsec -c e2e_tests/provider_cfg/mbed-crypto/config.toml
+ '[' -z 8 ']'
+ sleep 5
+ pgrep parsec

this ./target/debug/parsec -c e2e_tests/provider_cfg/mbed-crypto/config.toml runs after wait_for_service??

I think this is due to CI's way of logging, in the ci.sh script it's definitely in the right order

[tgonzalezorlandoarm]

https://github.com/parallaxsecond/parsec-openssl-provider/actions/runs/8144271957

[tgonzalezorlandoarm]

https://github.com/parallaxsecond/parsec-openssl-provider/actions/runs/8173626578