Rebranding code in libvalkey

[michael-grunder]

I left Redis in-tact in things like the CHANGELOG.md and all the copyright headers but think I got everything else.

Part of #11

[bjosv]

In the PR for the cluster code Viktor had a fair comment about renaming files multiple times. Maybe we should move the renamed files to src/ directly here too?

[michael-grunder]

To libvalkey/src in this PR or to the root?

[bjosv]

To libvalkey/src in this PR or to the root?

To <repo root>/src/, then we would have them in the right place from start. Then I'll move the cluster source there aswell so we have them mixed.

[zuiderkwast]

LGTM

Reviewed in a scrolling speed of 1 page/second. 😎

Let's merge this and fix stuff afterwards? I believe that allows more people to work in parallel.

Some things to consider in the future follow-ups:

• Move fuzzing to /tests/
• Move examples to /examples/ or are they actually tests?
• What include files to we like the users to see?
  • <valkey/valkey.h> sync API, e.g. valkeyCommand()
  • <valkey/async.h> async API, e.g. valkeyAsyncCommand()
  • <valkey/cluster.h> Cluster sync API, e.g. valkeyClusterCommand()
  • <valkey/cluster-async.h> e.g. valkeyClusterAsyncCommand()? (or is it -AsyncCluster-?, i forgot)
• Move exported API include files to /include/? (Doesn't affect where gets installed.)
  • Adapters .h files to /include/adapters/?
• Rename SSL to TLS?
• Or is it better to change as little as possible, so users can predictably just change "redis" to "valkey" and then everything else will work out of the box?

[michael-grunder]

Sounds good. Feel free to merge.