Simplify MCP setup by publishing to PyPI and adding a console entry point

[VIEWVIEWVIEW]

Please see #53

This PR does the following things:

• rename the package from "mariadb-server" to "mariadb-mcp". Mariadb-server is not what this thing is, and I think "mariadb-mcp" would be more in line with current naming conventions of MCPs.

  mcp/pyproject.toml

  Line 2 in 3c533f6

  name = "mariadb-server"

• Add console entry point in pyproject.toml, so you can simply run uvx mariadb-mcp. Ex.: https://github.com/VIEWVIEWVIEW/mariadb-mcp/blob/afb3f2a9df70704d070e97b21b1eb85b1dc6ae29/pyproject.toml#L21-L22
• Add setuptools config to pyproject.toml, require for PyPi publish job Ex.: https://github.com/VIEWVIEWVIEW/mariadb-mcp/blob/afb3f2a9df70704d070e97b21b1eb85b1dc6ae29/pyproject.toml#L21-L26
• Setup project on a PyPi account and "trusted publisher" (https://docs.pypi.org/trusted-publishers/adding-a-publisher/) (Needs to be done by the maintainers, please)
• Setup a Github action for publishing on PyPi. Ex.: https://github.com/VIEWVIEWVIEW/mariadb-mcp/blob/main/.github/workflows/publish-pypi.yml
• Change README to prefer uvx mariadb-mcp
• Push version number in pyproject.toml