Mysql: try to fixed mysql bug with update to 9.6 and delting old method of native password

[MaximilianJahns]

Removes deprecated --default-authentication-plugin=mysql_native_password flag which was removed in MySQL 9.x, and bumps the image to 9.6.0.

[ArneTR]

@MaximilianJahns
The scenario fails. Did you try to run it?

Are you in the newest version of the GMT?

Error I get:

Exception_context (SchemaWrongKeyError): Wrong key 'sci' in {'name': 'HammerDB Postgres benchmark', 'author': 'Didi Hoffmann >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Traceback (most recent call last):
File "/home/gc/green-metrics-tool/lib/schema_checker.py", line 241, in check_usage_scenario
usage_scenario_schema.validate(usage_scenario)
File "/home/gc/green-metrics-tool/venv/lib/python3.12/site-packages/schema/__init__.py", line 519, in validate
raise SchemaWrongKeyError(message, e.format(data) if e else None)
schema.SchemaWrongKeyError: Wrong key 'sci' in {'name': 'HammerDB Postgres benchmark', 'author': 'Didi Hoffmann
job.process(docker_prune=config['cluster']['client']['docker_prune'], full_docker_prune=config['cluster']['client']['full_docker_prune'])
File "/home/gc/green-metrics-tool/lib/job/base.py", line 74, in process
raise exc
File "/home/gc/green-metrics-tool/lib/job/base.py", line 64, in process
self._process(**kwargs) # uses child class function
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/gc/green-metrics-tool/lib/job/run.py", line 77, in _process
self._run_id = runner.run()
^^^^^^^^^^^^
File "/home/gc/green-metrics-tool/lib/scenario_runner.py", line 2891, in run
raise exc
File "/home/gc/green-metrics-tool/lib/scenario_runner.py", line 2790, in run
self._initial_parse()
File "/home/gc/green-metrics-tool/lib/scenario_runner.py", line 698, in _initial_parse
schema_checker.check_usage_scenario(self._usage_scenario_original)
File "/home/gc/green-metrics-tool/lib/schema_checker.py", line 250, in check_usage_scenario
raise SchemaError(f"Your compose file does contain a key that GMT does not support - Please check if the container will still run as intended. If you want to ignore this error you can add the attribute `ignore-unsupported-compose: true` to your usage_scenario.yml\nError: {error_message}") from e
schema.SchemaError: Your compose file does contain a key that GMT does not support - Please check if the container will still run as intended. If you want to ignore this error you can add the attribute `ignore-unsupported-compose: true` to your usage_scenario.yml
Error: ['Wrong key \'sci\' in {\'name\': \'HammerDB Postgres benchmark\', \'author\': \'Didi Hoffmann >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>