feat(aws-s3): Migrate S3 Upload task to use Data.From facility

[KarthikReddyMaru]

This PR migrates the Upload task to use the standardized Data.From pattern as part of the ubiquitous from initiative.

closes kestra-io/kestra#12345

What changes are being made and why?

The Upload task previously used manual Object type handling with pattern matching for Collections, JSON arrays, and single strings. This PR standardizes it to use the Data.From facility:

Key Changes:

• ✅ Implement Data.From interface for consistency with other plugins
• ✅ Replace manual parsing with Data.from().readAs() reactive API
• ✅ Update Schema annotations to use Data.From.TITLE and Data.From.DESCRIPTION
• ✅ Remove internalStorageURI = true from @PluginProperty (now handled by Data API)

Implementation Details:

The migration uses a hybrid approach due to a Data API limitation:

[KarthikReddyMaru]

Hi @Malaydewangan09

Quick heads up: I've posted about a Data API limitation with String.class in the sub issue kestra-io/kestra#12345. This affects the implementation approach. Would be great if you could check that before reviewing. Thank you! 🙏

[KarthikReddyMaru]

Hi @Malaydewangan09, could you please review this PR when you have time? I'd appreciate any feedback or guidance on the changes. Thanks!

[Malaydewangan09]

Sure @KarthikReddyMaru, thanks for the contribution! 🚀

[Malaydewangan09]

Looks quite OK to me 👍, @fdelbrayelle do you have any points to put up here or if I am overlooking something?

[fdelbrayelle]

Check my comment

[KarthikReddyMaru]

Hi @fdelbrayelle

Unfortunately removing those lines breaks JSON array parsing. Data.readAs(String.class) hits the clazz.isAssignableFrom(from.getClass()) check before JSON parsing, so it returns the entire JSON string as one element instead of parsing it. I've detailed this limitation with debug evidence in kestra-io/kestra#12345 (comment). The explicit JSON handling is necessary to work around this String.class short-circuit behavior.