Add ImageVector support to the preference datastore ui

[lm41]

This is required to fully switch to ImageVectors in the https://github.com/florisboard/florisboard project.

The old method of using Drawable Ids is still supported. Consideration may be given to deprecating these methods.

[patrickgold]

Thanks a lot for the changes.

I have reviewed them and am currently a bit torn apart about the way you've implemented the image vector support. What if we take a bit of convenience away from the composables and only expose the following attributes:

icon: @Composable (() -> Unit)? = null,
iconSpaceReserved: Boolean,

on each composable that has an icon? Basically we (almost) eliminate the need for maybeJetIcon, we only need the ({ }) composable if iconSpaceReserved=true. What we definitely save is duplication of all composables which reduces maintainability issues going on. In the FlorisBoard code base we can introduce a convenience function which makes an icon composable from a drawable id or an ImageVector. Would also solve the awkward need to specify imageVector=null on the composable if I see it correctly.

You do not need to mark any of the old functions as deprecated as jetpref has not had any stable release yet so breaking API changes are expected.

[lm41]

I've thought about it a bit and I think I've found a good option via the JetIcon interface.
This also enables additional support for your own icon implementations (such as custom painter etc.)

[patrickgold]

Thanks a lot for the changes! I've had a look at the changes and like the JetIcon idea! There are some issues/questions though that need clarification or fixing. (See comments)

[patrickgold]

Thanks for the fix, I've re-reviewed your incoming changes. After this iteration I think the code should be ready to merge

[patrickgold]

Reviewed again and tested out locally, everything checks out fine, merging into main. Thanks for the efforts!

[patrickgold]

For test using you'd have to use snapshots, here temporarily enable the jitpack repo in the core repo and then use the version table from here to grab a snapshot version (easier than using maven snapshots)