removing FluentAssertions from dependencies

[Sa1Gur]

Issue link

Due to recent license change seems reasonable to remove FluentAssertions (although there is not direct danger fluentassertions/fluentassertions#2956). Still it is just couple of code lines

Checklist

Before submitting the PR make sure the following are checked:

• This Pull Request is related to one issue.
• Commit message has a detailed description of what changed and why.
• Tests are added or updated.
• CHANGELOG.md and documentation files are updated.
• Destination branch is correct - main or release
• Create merge commit if merging release branch into main, squash otherwise.

[asafpamzn]

Thanks for contributing.
Looks good to me.

[Muhammad-awawdi-amazon]

Hey @Sa1Gur , thanks for the contribution :) appreciated

• Could you provide more details about the license change?

• is this change part of a larger effort to standardize on xUnit assertions across the project? If so, are there plans to update other files?

[Sa1Gur]

1. I’m not entirely certain which link is the most appropriate, but this one seems sufficiently official: Fluent Assertions Releases. Essentially, Fluent Assertions has transitioned to a paid model for commercial use. While this shouldn't currently impact Glide, we might inadvertently restrict our product users over just 5 lines of code. Alternatively, we could avoid updating, but that doesn’t seem ideal either.
2. I plan to create a PR to update the xUnit version (now that v3 is finally out) and review our usage in conjunction with these changes.

[Muhammad-awawdi-amazon]

Awesome @Sa1Gur
i'll create a github issue and assign it to you to track the progress 😄
Thanks for bringing this up