ImageResource type seems to be conflicting with Xcode 15's new type, causing a compile error.

[JohnnyTseng]

Check List

• [v] I have read the wiki page and cheat sheet, but there is no information I need.
• [v] I have searched in existing issues, but did not find a same one.
• [v] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description

Kingfisher's ImageResource type name conflicts with new type name generated by Xcode 15.
This code raises an error:

let resource = ImageResource(downloadURL: URL(string: "https://www.google.com.tw")!)
KingfisherManager.shared.retrieveImage(with: resource, options: []) { [weak self] result in }

What

Xcode 15 introduces a new feature that allows developers to use Image assets without hard-coding the file name, example:
Old way:

UIImage(named: "demoAsset")

New way:

UIImage(resource: .demoAsset)

This is done by Xcode, generating the symbol for developers.
And because the type of property resource is also called ImageResource, this conflicts with Kingfisher's ImageResource symbol, causing a compile error.

Reproduce

Clone and build this project: https://github.com/JohnnyTseng/KingfisherXcode15Demo

Other Comment

Environment:

• Xcode 15.0 beta (15A5160n)
• macOS Ventura 13.4

Note that if you setup a new project to reproduce this issue, remember to set deployment target to < iOS 17.0
It seems like with deployment target iOS 17.0, Xcode adds an extra namespace called DeveloperToolsSupport before ImageResource, causing we can't reproduce this issue.

[JohnnyTseng]

Simply changing the name ImageResource would be a simple solution, but it introduces a breaking change, I'm not sure how we could deal with this in a better way 🤔

[onevcat]

This was discussed in #2090 and I pushed some commits in #2092

There is no good way to solve it without any pain. Hopefully the related changes can improve the transition experience a bit.

[JohnnyTseng]

Ooops, I've searched Xcode 15 and related words, didn't notice this issue, sorry for the duplicated issue 😅