Feat: Logging alternative to #547

[Kigstn]

What type of pull request is this?

• Non-breaking code change
• Breaking code change
• Documentation change/addition
• Tests change

Description

This is an alternative solution to #547, attempting to solve the logging problem.

This PR allows users to pass their own logger at client initialisation. The passed logger is saved in both the client and naff.constants.

This has several benefits;

1. users don't have to do nasty stuff at the very start of their code to overwrite the naff logger before naff does anything with it
2. custom loggers, like rich.logging or file handlers can be easily used
3. users have more direct and easier access to the logger via both client.logger and naff.consts.logger, instead of having to logging.getLogger(logger_name) every time they want to use it
4. naff devs have an easier time as well, since they can import the logger from anywhere as well

Changes

• a logger obj is now defined in naff.consts which is overwritten by the logger the user passes to Client

Checklist

• I've formatted my code with Black
• I've ensured my code works on Python 3.10.x
• I've tested my code

[LordOfPolls]

On-Hold pending discussion and conflict resolution

[Kigstn]

Ready for review

[LordOfPolls]

It hurts me calling it logger

[LordOfPolls]

/ok-to-test

[Kigstn]

It hurts me calling it logger

It hurts me calling it log