Add support for running MCP server initialization code

Clients will typically invoke ListTools right after client initialization is complete. We don't attempt to run this code as a notification handler because those don't have access to the server instance and therefore are not very useful.

Running just before tools list is a good spot for post-initialized and before things can actually start running.

Note that doing elicitation in this context won't work, but other notifications/logging to the client should be perfectly functional at this stage.

Add extension to register a tool individually

This does away with the need to have a type for the individual tools at all.

Bump to latest AI extensions

Bump to latest AI extensions

Adjust namespaces

+Mᐁ includes

Add standard badges

+Mᐁ includes

Add project icon for package