Set correct pin-value format in tests

[sarroutbi]

Description

As described in #360, correct format for pin-value option in URI is for it to be after '?', rather than as an additional URI path. This change sets the values appropriately in tests to identify possible parser issues

Fixes #360

Checklist

• Test suite updated for functionality tests

Reviewer's checklist:

• Any issues marked for closing are addressed
• There is a test suite reasonably covering new functionality or modifications
• Code conform to coding style that today cannot yet be enforced via the check style test
• Commits have short titles and sensible commit messages

[simo5]

Thanks, looks good!

[Jakuje]

Should we also update the parser to not accept the "bad" values or at least warn the user he did something "wrong"?

[simo5]

No, we already have this out there, we'd unnecessarily break users.
We should just make sure to change docs to use the correct format, but allowing pin to be passed in the path is fine, it doesn't cause any obvious issues.

[simo5]

To be clear,
I would not reject a PR to emit a warning in the debug/openssl log for pin-value and/or path values in the incorrect place, but it is not a priority.