adding some icons and metadata for fruitjam os

[FoamyGuy]

These icon and metadata.json files get used by the fruit jam OS launcher.

Other changes include:

• swapping a few projects to use the adafruit_fruitjam library to request a display size instead of assuming the appropriate one, or manually initializing it.
• change the behavior of exiting in a few cases to integrate with the fruit jam OS launcher better.
• use adafruit_usb_descriptors helper to find appropriate mouse USB interface instead of assuming the first one found is correct.

[TheKitty]

@FoamyGuy - would it be better that the request_display_config routine be in displayio rather than a Fruit Jam library when it might be used in non-Fruit Jam projects?

[FoamyGuy]

@TheKitty I think it's not applicable for most of normal displayio stuff because typically hardware displays like OLED, LCD, eink etc, have a fixed resolution that they need to be initialized at. picodvi is different in that it allows a few different resolutions and configurations.

I think there could be some merit in adding a helper function like this to picodvi in the core, especially if we foresee a future where larger resolutions get supported as well. Though it is a bit tricky because this code also relies on hard-coded pin names (https://github.com/adafruit/Adafruit_CircuitPython_FruitJam/blob/4c3a50d0bff9dd5f93e8f2fae395d7834d5111b0/adafruit_fruitjam/peripherals.py#L66-L73) I believe the pin naming scheme used is the same for the Metro RP2350 and the Fruit Jam so both of those devices could use this helper but newer or 3rd party devices would only be able to use if they match this naming / usage of the data pins.

It would be essentially codifying this pin naming/usage into a defacto default "standard" of sorts for picodvi moving forward. Though user code can always fall back to the normal more specific API to provide their own different pins as well.