[superseded by #1516] Add CarPlay support

[llim1]

Changes

Adds CarPlay support using flutter_carplay package.

Todo before merging

• install dependencies & configure iOS project
• basic now-playing screen
• library tab: albums list
• library tab: artists list
• library tab: genres list
• library tab: playlists list
• library tab: tracks list
• search tab (likely requires changes to flutter_carplay)
• recently played tab
• home tab?
• support offline mode
• replace static text with localizations
• rich 'now-playing' screen inc. queue management + album art (likely requires changes to flutter_carplay)
• now-playing icon on list entries

Known issues

Will cross off issues here once they are addressed.

• flutter_carplay loads images from web URIs but file URIs are broken despite file paths being listed as supported
• 'now-playing' screen has inconsistent behaviour on iOS simulator. Need build to physical hardware to test
• 'now-playing' button in root tab view is missing the icon, despite being clickable

• Translations

• Reset Settings

• Extended CONTRIBUTING.md

Related Issues

• Closes Carplay support? #24

[Chaphasilor]

@llim1 there's another PR for this (#1480), does that help you at all? I'm guessing you PR probably has more thoughtful UI and integration with the existing codebase, but I haven't looked into it yet.

[llim1]

@llim1 there's another PR for this (#1480), does that help you at all? I'm guessing you PR probably has more thoughtful UI and integration with the existing codebase, but I haven't looked into it yet.

Looks like that other PR does a swift native implementation instead of the carplay_flutter module I'm using. Given the limitations of this library I figure some native code will always be needed, so the 'ideal' solution will probably lean more towards their PR. Though, I have not looked at it closely yet.

I should have some time to revisit this project soon, first task will be to do a proper review of #1480. I did also have plans to optimize the carplay and android auto code into a single API, which could probably be done on top of either implementation.

[Chaphasilor]

@llim1 I'll go ahead and close this since your changes are incorporated into #1516 now, and it seems like there's no point in keeping this original PR around.
I'll give you a shoutout in the release notes once this lands, of course!