Update AWSSDK.S3 package version

[nazem0]

Updated AWSSDK.S3 package version from 4.0.7.2 to 4.0.102.3.

Description

Resolves #26038

Updated the AWSSDK.S3 dependency to 4.0.102.3.

I tested the change in two ways:

Tested it in my own existing ABP project by updating the package and running the application and EF Core migration workflow.
Downloaded the library source, applied the package version change, built it, and tested the updated package independently.
No breaking changes are expected.

Checklist

• [ ✅] I fully tested it as developer / designer and created unit / integration tests
• I documented it (or no need to document or I will create a separate documentation issue)

How to test it?

Update AWSSDK.S3 from 4.0.7.2 to 4.0.102.3.
Restore and build the project.
Run the application and verify that the AWS S3 integration continues to work.
Run an EF Core migration using the Visual Studio Package Manager Console, for example:
Add-Migration TestMigration
Verify that the migration is generated successfully without the AWSSDK.Core NU1901 warning causing the command to terminate.
Verify that existing S3 functionality continues to work as expected.

[nazem0]

@maliming

[maliming]

Hi @nazem0,

Thanks for the PR.

Two things before we merge this:

1. This needs to target rel-10.7 so it ships with the 10.7 release - dev is already 10.8. Retargeting this PR won't work cleanly, since the head branch is your fork's dev and the diff would pick up every commit that dev has over rel-10.7. Could you open a new PR from a branch based on rel-10.7?

2. Please also bump AWSSDK.SecurityToken to 4.0.100.10 in the same file. It still asks for AWSSDK.Core [4.0.0.28, 5.0.0), so the patched AWSSDK.Core currently comes from the S3 package alone - if someone pins S3 to an older version in their own project, NU1901 is back.

Thanks

[nazem0]

Updated AWSSDK.S3 package version from 4.0.7.2 to 4.0.102.3.

Done. I’ve made the changes and opened a new PR: #26040.