[FR]Add Grouping Support for Grid View Databases in the Web Client

### Feature Description

Please add support for grouping records in Grid View databases in the AppFlowy Web client.

This functionality is currently available in the Desktop client, but the same database view does not provide grouping options when accessed through the Web client.

Current Behavior

In the AppFlowy Desktop client, users can group Grid View database records by a property/field.

In the Web client:

The Group option is not available.
Existing grouped database views do not provide the same grouping controls as Desktop.
Users must switch to the Desktop client to create or manage grouped Grid Views.

### Use Cases

Grouping is especially useful for databases such as:

Tasks grouped by Status
Contacts grouped by Company
Projects grouped by Owner
Opportunities grouped by Stage
Meetings grouped by Customer
Records grouped by Category or Type

Without grouping support in the Web client, users working across both Desktop and Web do not have feature parity and must return to the Desktop application to manage these views.

### User Impact

The lack of Grid View grouping in the Web client creates a significant usability gap between the Desktop and Web experiences.

Users who rely on grouped database views to organize information by status, customer, owner, category, project stage, or other properties lose that organization when accessing AppFlowy through the Web client.

This impacts users by:

Requiring them to switch back to the Desktop client to properly work with grouped databases.
Making the same database behave differently depending on which client is being used.
Reducing the usefulness of the Web client for users who primarily access AppFlowy through a browser.
Making it harder to quickly understand and navigate larger databases because records are presented as one continuous list instead of logical groups.
Creating friction for teams where some users use the Desktop client while others use the Web client.
Limiting the Web client as a complete alternative to installing the Desktop application.

For self-hosted deployments, this can be particularly important because organizations may want to provide users with browser-based access without requiring every user to install and maintain the Desktop client.

Adding grouping support would significantly improve Desktop/Web feature parity and make Grid View databases much more practical for users who depend on the Web client.

### Potential Implementation Ideas

_No response_

### Additional Context

_No response_