Support to use a custom database number

[ardecvz]

What is the purpose of this pull request?

Support to use a custom database number.

What changes did you make? (overview)

Parse --redis_url (ANYCABLE_REDIS_URL or REDIS_URL) using the rueidis standard utility.

Is there anything you'd like reviewers to focus on?

WARNING! This could be a potentially breaking change. Prior to this update, AnyCable Go did not support database numbers but allowed them in the REDIS_URL. As a result, if a user had set a URL with a database number, all data would still be written to the default database (0). After upgrading, this will break the existing user setup by starting to write data to the specified in the URL database, potentially leaving remnants in the old one.

@palkan, it's critical for you to assess how important the data in the storage is and decide on the appropriate path for data migration (whether that be discarding the old data, issuing a warning, performing automatic migration, etc.).

Checklist

• I've added tests for this change
• I've added a Changelog entry
• I've updated documentation

Fixes #188

[ardecvz]

@palkan The extended test conformance output is fixed there - anycable/anyt#7
Anyway, I'm looking into the failures.

[ardecvz]

Locally no errors with NATS and NATS Embedded

[ardecvz]

It seems that the hidden errors are timeouts - Anyt::Client::TimeoutError
I've reproduced errors locally with another conformance suite (https), but it seems to be broken in the master too :'(

[palkan]

Locally no errors with NATS and NATS Embedded

Have you tried upgrading nats-pure?) (I guess, @Envek knows what happened 😁)

UPD: nats-io/nats-pure.rb#132

[palkan]

Thanks! I pinned nats-pure to an older version for now. Merging this and hope all tests will pass now.

[palkan]

Okay, this is a real one: https://github.com/anycable/anycable-go/actions/runs/6154293794/job/16699510933

@ardecvz Could you please take a look? (And propose a follow-up PR?)

[ardecvz]

Of course, NATS hides these failures.
And did you see the WARNING in the PR description?
This change may break user setups when we're starting to use the proper database number - is it OK to lose data remnants there?

[palkan]

is it OK to lose data remnants there?

Yeah, it's fine. All the data we store has TTL.