Feature Request：GBase8s DB #258 add support GBase8s DB

[617206652]

Overview:
This PR adds support for the GBase8s database.

Key Changes:
Added the GBase8s dialect directory, and the framework has also incorporated the processing procedures for GBase8s.

Related Issue: #258.

Components required for the Windows：
https://www.gbase.cn/download/gbase-8s-1?category=DRIVER_PACKAGE
download：clientsdk_3.6.3_3X3_1_ee39df_WIN2003_x86_32.ZIP

Checklist:
Local tests passed.

No breaking changes identified.

[madelson]

This should not be included

[madelson]

Remove

[madelson]

This library isn't well-established enough for use here (< 1K downloads, < 2 months old).

Looks like Odbc seems to be the more common pattern for GBase interactions in the NuGet world

[617206652]

I'm sorry for the delayed reply. I've been busy with project matters recently and didn't handle your response in time.

Our product was only recently published on NuGet, but it has actually been in use for a long time. The reason is that our product was not allowed to be released publicly on the internet before. Now, to improve our ecosystem, we have pushed it out recently.

[madelson]

Remove all Console logs

[madelson]

Thanks for raising this PR @617206652 .

After reviewing this and looking into GBase a bit more, I have concerns about being able to take on long-term support for GBase at this time.

However, this made me reflect on the fact that of the code written here, the only thing that's really specific to GBase is GBaseDbmsLock.

This led me to come up with a proposal for a new extensibility layer which would basically expose the helpful internals from DistributedLock.Core to any ADO.NET-based implementation in a way that would make implementation very easy.

Then the ecosystem would look like this:

IDistributedSynchronizationProvider provider = new AdoDistributedSynchronizationProvider( // part of core DistributedLock
    connectionString,
    GBaseSynchronizationDriver.Instance); // extension library, e.g. [YourName].GBaseSynchronizationDriver

If this interests you, I think it would be very easy to pivot the work you've done here to become the implementation of the Ado extension layer.