chore(dependencies): Update Media3 to 1.5.0

[EverydayPineapple]

I have a strange issue with the current release of mux-player-android that's forcing me to exclude the Media3 group from my dependencies. I haven't fully traced the issue but it's something to do with the fact that I end up with two versions of some of Media3 and Activities aren't being fully destroyed where they were before. It's very strange.

I've done the following for now

implementation(libs.mux) {
    exclude(group = "androidx.media3") 
  }

... but would be nice not to have to.

I believe the following PR is all you need to update to 1.5.0 but feel free to let me know otherwise.

[daytime-em]

@EverydayPineapple Thank you for your contribution! I'll probably be able to get this deployed today.

Just to make sure: Did updating media3 to v1.5.0 fix the Activity lifecycle issues? We'll verify either way, but it's always good to have more evidence 😄

[EverydayPineapple]

@EverydayPineapple Thank you for your contribution! I'll probably be able to get this deployed today.

Just to make sure: Did updating media3 to v1.5.0 by itself fix the Activity lifecycle issues? We'll verify either way, but it's always good to have more evidence 😄

Thanks very much.

Yes, the update to 1.5.0 Media3 fixed my lifecycle issues. I found that because I didn't specifically import the media3 IMA module, I was getting the version Mux referenced. Unfortunately I don't have the time to dig deeper into the actual issue to give you anything more than I was having problems with Activities not being destroyed properly.

Once I override the version, and ensure my app only has 1.5.0 Media3 packages, my tests start passing again.

[daytime-em]

@EverydayPineapple Wonderful! We'll close this out then.

This fix should be available in v1.3.0 of Mux Player, which will deploy in the next half hour or so.