[Feature Request]: More robust API fallback strategy

[ChunkyProgrammer]

Guidelines

• I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
• I have searched the documentation for information that matches the description of the feature request I want to file, without success.
• This issue contains only one feature request.

Problem Description

I think it'd be useful to have a more customizable fallback strategy that could fallback to multiple different invidious instances if necessary.
related: #1791

This will also be useful when running FreeTube without electron ex: FreeTube Cordova.
MarmadileManteater#5

If this is implemented well (ex: maybe adding a url type) it could make it a lot easier to add support for Piped in the future.

Proposed Solution

Some sort of re-orderable list in the setting for fallbacks.

The list will contain invidious urls as well as 'local api' so people can have multiple fallbacks if an invidious instance fails before switching to the Local API.

Alternatives Considered

None

Issue Labels

ease of use improvement, improvement to existing feature

Additional Information

No response

[efb4f5ff-1298-471a-8973-3d47447115dc]

I think it'd be useful to have a more customizable fallback strategy that could fallback to multiple different invidious instances if necessary.

Yes please, this issue is a gem. Why should a user be tied to the local api when their favorite instance doesnt work. Just give them a 2nd instance as fallback.

Edit: I think we can start working on this after #3559 is merged

[mooleshacat]

I had opened a duplicate #3408, asking for a multiline textbox so I could list two private instances then a public instance at the end. I've now closed it. Apologies :)

Also a checkbox to use either fastest instance, or use them in the order they are listed (as a fallback)

I appreciate the hard work you do on this project 👍