fix: handling of Optional[...] in command option type resolution

[Lumabots]

Summary

This PR fixes an issue where using Optional[T] or T | None as a parameter annotation in command options would raise:

TypeError: Invalid class <class 'NoneType'> used as an input type for an Option

Since providing option=None already marks the option as optional (required=False), including None in the type annotation (e.g., str | None) is unnecessary inside the option type itself. Therefore, the code now removes NoneType from the input type annotation without raising an error, allowing the typing to remain clean and correct.

this is now valid

@bridge.bridge_option(name="guild_id", autocomplete=GuildSetup.guild_autocomplete)
async def banner(self, ctx: LumabotContext, guild_id: str | None = None):

Information

• This PR fixes an issue.
• This PR adds something new (e.g. new method or parameters).
• This PR is a breaking change (e.g. methods or parameters removed/renamed).
• This PR is not a code change (e.g. documentation, README, typehinting,
  examples, ...).

Checklist

• I have searched the open pull requests for duplicates.
• If code changes were made then they have been tested.
• I have updated the documentation to reflect the changes.
• If type: ignore comments were used, a comment is also left explaining why.
• I have updated the changelog to include these changes.

[Paillat-dev]

If it works it works but options really are a mess...