oracledb thin client - support locale specific date and number conversion

Personne n'a encore pris cette issue.

Currently there is no native support for the python oracledb module, so this issue occurs when using "connect using custom params" mode (see #173 for connection example).
There is a problem if the test data used in Robot Framework has some regional format different from the Oracle DB.
For example, with decimal/float number and dates:
- The standard English Oracle format for a decimal number is point-based - e.g. `123.45`.
- But in some other languages/regions (e.g. in Germany) the comma-based format is used - `123,45`.

So before I save some local values to the database or compare them with the database values, there is some conversion to be done.
**Currently it has to performed manually**.
### Maybe there is a better way?

The thin mode of the oracledb client doesn't support Oracle Globalization variables (see the full comparison between thin and thick clients [here](https://python-oracledb.readthedocs.io/en/latest/user_guide/appendix_a.html#featuresummary)).
So they advice to use the python globalization support - and provide an [example](https://python-oracledb.readthedocs.io/en/latest/user_guide/globalization.html#thin-mode-locale-aware-number-and-date-conversions).

Also I'm not sure, but maybe this issue is relevant also for other databases?

Commencez par le mode de connexion custom-params et l’exemple de connexion de l’issue #173, puis lisez l’exemple de globalisation lié de python-oracledb thin-mode. Définissez comment la conversion des dates et des nombres tenant compte de la locale doit fonctionner pour les données de test de Robot Framework, et précisez si le périmètre inclut des bases de données autres qu’Oracle.

Rédigé par le modèle d'indexation à partir du texte de l'issue.