fix: more comprehensive query param encoding

[GuyBrush385]

API calls have no comprehensive param encoding.
For most params this is not really an issue but like "find component" can cause mismatches.

[tngraf]

Thanks for the PR. Did you test with a real SW360 instance that all parmater encoding works as it should be?
I am asking because some years ago the SW360 REST API was not able to have correctly encoded parameters
everywhere...

[GuyBrush385]

I now gone throught the changes the best to my knowledge about sw360 and tested them as good as I could against a real instance.
My guess that the queries build with _add_param did not have the issue with the "not able to process encoded call" but I only touched those. There are quite a few other calls which still just do some basic string concat.