New immudb instance with S3 options turned on cause a startup error

[NikitaSmall]

What happened
When a new immudb instance (taken from the current master) starts up, the error appears

immudb 2023/11/21 14:21:03 ERROR: unable to initialize remote storage: remote storage does not have expected identifier
Error: remote storage does not have expected identifier

What you expected to happen
A new immudb instance starts, and stores the data in S3. No error should appear.

How to reproduce it (as minimally and precisely as possible)
Spin up immudb with the configuration to connect to S3. Flag S3ExternalIdentifier is set to true.

Environment
immudb version: 1.9DOM1

Additional info (any other context about the problem)
It seems that I am the person who could actually add this bug to the system. If I have time, I will release a fix

[angelAtSequent]

This is also happening on 1.9DOM2. Any chance to have this fixed?