refactor!: prevent from confusing and conflicting class names

[Gustl22]

Description

As some of the classes introduced in #1352 are quite generic and could conflict with other packages, we should rename them to be more specific to the package:

• Refactor GlobalEvent to GlobalAudioEvent
• Refactor PlayerEvent to AudioEvent
• Refactor Logger to AudioLogger
• Refactor LogLevel to AudioLogLevel

PlayerEvent was renamed to have the same scheme as GlobalAudioEvent and so that it is more applicable to Audio and not to all players in general (e.g. media or video player).

Checklist

• The title of my PR starts with a [Conventional Commit] prefix (fix:, feat:, docs:, chore: etc).
• I have read the [Contributor Guide] and followed the process outlined for submitting PRs.
• I have updated/added tests for ALL new/updated/fixed functionality.
• I have updated/added relevant documentation and added dartdoc comments with ///, where necessary.
• I have updated/added relevant examples in [example].

Breaking Change

This is a breaking change regarding the current master channel, but not the published versions.

• Yes, this is a breaking change.
• No, this is not a breaking change.

audioplayers

Before	After
GlobalEvent	GlobalAudioEvent
PlayerEvent	AudioEvent
Logger	AudioLogger
LogLevel	AudioLogLevel

audioplayers_platform_interface

Before	After
GlobalEvent	GlobalAudioEvent
PlayerEvent	AudioEvent

Related Issues

#1352