Allow rotation transformation without angle argument

[markatom]

Issue #, if available:

Related: github.com//issues/495

Description of changes:

This change enables the rotate filter to be used without an angle argument (e.g., filters:rotate()). The previous implementation would parse this as 0 and pass it to sharp.rotate().

The new implementation takes advantage of Sharp's behavior when rotate() is called without arguments:

1. It automatically determines the rotation angle from the EXIF data
2. It supports mirroring operations when needed
3. It removes the EXIF Orientation tag after applying the rotation

This change helps fix issues with images that contain EXIF orientation metadata but are displayed incorrectly in clients (e.g., browsers) that don't support EXIF orientation.

Reference: Sharp Documentation - rotate

Note: I have verified that the change works as expected, but additional unit tests may be needed to ensure proper coverage.

Checklist

• 👋 I have added unit tests for all code changes.
• 👋 I have run the unit tests, and all unit tests have passed.
• ⚠️ This pull request might incur a breaking change.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[markatom]

Related
• #537
• #540

[gsingh04]

Thanks @markatom for the PR and apologies for the delay here.

It does seem confusing to deviate from the sharp default behavior. One thing I noticed after applying your changes, we still need to update here as well.

dynamic-image-transformation-for-amazon-cloudfront/source/image-handler/image-handler.ts

Line 46 in 81f6c36

? sharp(originalImage, options).withMetadata({ orientation: metadata.orientation })

For me this seemed to interfere with the default behavior, probably because we overwrite the orientation metadata. After fixing this I was able to get following results

url - https://myDomain/filters:rotate()/myImage.jpeg
original image - Orientation: 6 (Rotated 90° CCW)
changed image -

[gsingh04]

We have added this to our backlog and will fix the behavior in upcoming releases.