Use standard UIImages instead of custom LazyImages

[ejensen]

Changes

Replaces the custom LazyImage type with standard UIImages. This enabled the use of symbol images (SF Symbols), better supports dynamic image configurations, and reduces memory use.

This is a non-breaking change since there is a deprecated typeAlias for LazyImage that will automatically suggest migration to UIImage:

References

• Apple Documentation - Configuring and Displaying Symbol Images in Your UI
• Apple Documentation - Providing Images for Different Appearances

Memory Usage

LazyImage	UIImage

Testing

• This change adds unit test coverage
• This change has been tested on the latest version of the platform/language or why not

Checklist

• I have read the Auth0 general contribution guidelines
• All existing and new tests complete without errors
• All active GitHub checks have passed

[Widcket]

@ejensen Thanks for the PR. Given that LazyImage is a public type, replacing it is a source breaking change regardless of Xcode helpers. So unfortunately I can't merge this.

[ejensen]

@Widcket Please see the note in the description about how this is not a breaking change because there is a typeAlias that handles references to LazyImage. Here's a screenshot of the sample app showing that existing references to LazyImage will continue to compile, and has a deprecation warning to optionally migrate to UIImage. I can remove the deprecation warning if you prefer.

This is a non-breaking change since there is a deprecated typeAlias for LazyImage that will automatically suggest migration to UIImage:

[Widcket]

@ejensen indeed, I missed it. Thanks!

[Widcket]

This is now out in v2.22.0.