Ensure ex_aws is set to version with transfer servers

[k1bs]

Now that ex_aws has merged my work adding the transfer family server list, ensure we use that version (I put a <3 just to be safe)

I'll tag this v0.2.0 when it gets merged.

[coderabbitai]

Walkthrough

Updated the dependency version constraint for ex_aws in mix.exs from a pessimistic version spec (~> 2.1) to an explicit lower and upper bound (>= 2.6.1 and < 3.0.0). This is a configuration-only change with no functional or control-flow modifications.

Changes

Cohort / File(s)	Summary
Dependency version constraint update mix.exs	Updated {:ex_aws} dependency constraint from "~> 2.1" to ">= 2.6.1 and < 3.0.0"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Verify that the new version range (>= 2.6.1 and < 3.0.0) is compatible with the project's codebase and other dependencies
• Confirm the reasoning for the shift from pessimistic to explicit bounds

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating ex_aws to a version with transfer servers, which matches the dependency constraint update in mix.exs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The description clearly explains the purpose of updating the ex_aws dependency to include transfer family server list support, with a specific version constraint rationale.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch k1bs/4754/update-to-latest-exaws

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[fastjames]

🍰