Remove FluentAssertions dependency and standardize on xUnit assertions

[Muhammad-awawdi-amazon]

Background

Due to recent license changes in FluentAssertions (see fluentassertions/fluentassertions#2956 and Fluent Assertions Releases), it's prudent to remove this dependency from our project. While there's no immediate danger, this change will prevent potential future restrictions on our users.

Current Usage

FluentAssertions is currently used in a few places in our test code. For example:

_ = (await client.SetAsync(key, value))
    .Should()
    .Be("OK");
_ = (await client.GetAsync(key))
    .Should()
    .Be(value);

Proposed Changes

Remove the FluentAssertions dependency from the project.
Replace all FluentAssertions assertions with standard xUnit assertions.
Update the files to remove the FluentAssertions package reference.

Example of Changes

Assert.Equal("OK", await client.SetAsync(key, value));
Assert.Equal(value, await client.GetAsync(key));

The plan to update to xUnit v3. This will involve reviewing our assertion usage and potentially taking advantage of new xUnit features.
Consider creating a project-wide guideline for managing test dependencies and assertion styles to ensure consistency across all files.

[Muhammad-awawdi-amazon]

@Sa1Gur

[Yury-Fridlyand]

Fixed by #3013

[Muhammad-awawdi-amazon]

@Yury-Fridlyand I dont think its completed yet, check has to be done for the rest of the wrappers, and as @Sa1Gur mentioned, he will update to xUnit v3

[Yury-Fridlyand]

Oh, excuse me my misunderstanding.