feat: allow enabling of specific feature groups + adds storage tools

[Ngineer101]

What kind of change does this PR introduce?

This PR introduces feature groups that can be enabled or disabled when needed. In addition to project-ref and read-only, a new config option called features is added.

--features: Used to specify which feature groups to enable. Available features are: 'account', 'branching', 'database', 'debug', 'development', 'docs', 'functions', and 'storage'. Multiple features can be specified with comma separation (e.g., --features=database,debug,docs).

• When no project is specified: Defaults to ['account', 'database', 'debug', 'docs', 'functions']
• When a project is specified: Defaults to ['database', 'debug', 'docs', 'functions']

What is the current behavior?

Currently, all features are enabled by default. To better manage tool limits, this change allows users to enable only the feature groups they require, thus reducing the number of unnecessary active tools in the MCP server.

Based on this idea and this discussion.

[gregnr]

Great work @Ngineer101 🎉

There were a few small improvements I made to get this over the finish line:

• Use zod to simplify feature group validation
• Add development tools into the default list (forgot about this one earlier)
• Added tests for feature group tool filtering
• Added tests for CLI list parsing to make sure we cover edge cases
• Added more docs on feature groups
• Fixed update_storage_config tool returning nothing - Cursor didn't like this, so I replaced with { success: true }

[Ngineer101]

Awesome! 💯 :)