Bug: 'encrypted' flag not included in rooms.createDiscussion request when creating encrypted discussions

Description:

When creating a discussion with the Encrypted toggle enabled, the request sent to /v1/rooms.createDiscussiondoes not include the encrypted field in the payload. As a result, the created discussion may not be encrypted even though the user selected the encrypted option.

Steps to reproduce:

1. Open a channel.
2. Create a new discussion.
3. Enable the Encrypted toggle.
4. Click Create.
5. Inspect the request sent to /v1/rooms.createDiscussion.

Expected behavior:

The request payload should include:
encrypted: true

Actual behavior:

The request is sent without the encrypted property because the handleCreate function does not destructure the encrypted field from the form values.

Server Setup Information:

• Version of Rocket.Chat Server: 8.3.0-develop
• License Type: Community (dev build)
• Number of Users: 1 (local dev)
• Operating System: MacOS 26.2
• Deployment Method: Source / yarn dev (Meteor development server)
• Number of Running Instances: 1
• NodeJS Version: 22.16.0
• MongoDB Version: 6.10.0

Client Setup Information

• Desktop App or Browser Version: Chrome 145.0
• Operating System: MacOS 26.2

Additional context

Relevant logs:

Search the TypeScript codebase for the discussion-creation handleCreate function and trace the request sent to /v1/rooms.createDiscussion. Confirm that the encrypted form value is included in the payload when the Encrypted toggle is enabled, then verify the resulting request.