Fix "add podcast" FAB still visible under SpeedDial main FAB

[TacoTheDank]

Description

Taken from #6944.

• Fixed a UI problem where the "add podcast" FAB was still visible underneath the SpeedDial main FAB. It should be gone when the "multi select" option is active.
  - Fixed the SpeedDial main FAB being unlabeled in TalkBack. I used the workaround provided in TalkBack describes main FAB as "unlabeled button" leinardi/FloatingActionButtonSpeedDial#192 (comment).

Checklist

• I have read the contribution guidelines: https://github.com/AntennaPod/AntennaPod/blob/develop/CONTRIBUTING.md#submit-a-pull-request
• I have performed a self-review of my code
• My code follows the style guidelines of the AntennaPod project: https://github.com/AntennaPod/AntennaPod/wiki/Code-style
• I have mentioned the corresponding issue and the relevant keyword (e.g., "Closes: #xy") in the description (see https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
• If it is a core feature, I have added automated tests

[ByteHamster]

The setContentDescription part makes the app crash because it generates an endless loop. Apparently that is fixed by SpeedDialView 3.3.0. So we can basically decide if we want the content description to work (with 3.3.0) or focusing the correct menu item after opening to work (with 3.2.0). -.-

ERR: stack=java.lang.StackOverflowError: stack size 8MB
   at com.leinardi.android.speeddial.SpeedDialView.setContentDescription(SpeedDialView.java:242)
   at com.leinardi.android.speeddial.SpeedDialView.setContentDescription(SpeedDialView.java:242)
   at com.leinardi.android.speeddial.SpeedDialView.setContentDescription(SpeedDialView.java:242)
   at com.leinardi.android.speeddial.SpeedDialView.setContentDescription(SpeedDialView.java:242)
   at com.leinardi.android.speeddial.SpeedDialView.setContentDescription(SpeedDialView.java:242)
   at com.leinardi.android.speeddial.SpeedDialView.setContentDescription(SpeedDialView.java:242)
   ...

[TacoTheDank]

@ByteHamster Lol, that's annoying. I would argue the crash fix is probably higher priority, as the focus issue is merely unintended behavior. If you want, maybe you can fork the library and revert the commit that causes leinardi/FloatingActionButtonSpeedDial#194, and we can use that fork until it's fixed upstream? The library repo isn't very active, so...

Or, you could take the other option and remove the library altogether: #6948.

[TacoTheDank]

@ByteHamster How about this: I remove the setContentDescription change entirely and just make the PR about fixing the double FAB issue. That way at least the one fix can be merged :P

[ByteHamster]

Thanks!