Lazy config loading via Bot.start()

[PenguinBoi12]

Previously, Bot required a config at instantiation time, forcing library users to have a config path available at import time. This made it awkward to define a bot as a module-level singleton — a common and natural pattern — without immediately binding it to a config file.

This PR removes config from Bot.__init__ and moves it to Bot.start(), so users can now define and decorate their bot freely at module level and defer config to whenever they actually run it.

Changes:

• Bot.__init__ no longer accepts a config argument
• Bot.start() now requires a Config instance or path string
• _load_config is private since it's an implementation detail of start CLI updated to pass config through bot.start(settings.config)

Result: users can now define their bot as a clean singleton, decorate it freely, and let the runner handle the rest:

bot = Bot()

@bot.hook
async def on_ready():
    print("Ready!")

bot.run(config=Config(...))

... 

bot.run(config="config/bot.yaml")

[chrisdedman]

Could you either add an example or update the current examples (or one example) to reflect this change?

[PenguinBoi12]

Could you either add an example or update the current examples (or one example) to reflect this change?

I did, there's an example in the description of the PR. The doc will be changed after it's merged.

I might have forgotten the readme tho and examples, I'll change them.

[chrisdedman]

LGTM.

[chrisdedman]

LGTM