feat: Add credential-level option to disable session recording and logging

从 credentials/BrowserbaseApi.credentials.ts 开始，找到根据 credential 和 Browser Options 值构建 Browserbase 会话设置的节点执行逻辑。添加两个默认值为 false 的可选 credential 字段，并验证启用其中任意一个都会强制关闭其对应的设置，同时在禁用时保持当前行为不变。

Problem

When using the Browserbase node for back-office automation (e.g., expense processing, HR workflows, internal tools), browser sessions may display sensitive employee and business data. The current default behavior (recordSession: true, logSession: true) causes this data to be captured and stored on Browserbase servers for up to 30 days.

While individual workflow creators can toggle these options off in Browser Options, there is no way for an organization's n8n administrator to enforce this policy across all workflows using the same Browserbase credential.

Proposal

Add two optional boolean fields to BrowserbaseApi.credentials.ts that allow credential owners to force-disable session recording and logging for all workflows using that credential:

// credentials/BrowserbaseApi.credentials.ts
{
    displayName: 'Disable Session Recording',
    name: 'disableSessionRecording',
    type: 'boolean',
    default: false,
    description: 'Force-disable session recording for all workflows using this credential. When enabled, the per-node "Record Session" option is ignored.',
},
{
    displayName: 'Disable Session Logging',
    name: 'disableSessionLogging',
    type: 'boolean',
    default: false,
    description: 'Force-disable session logging for all workflows using this credential. When enabled, the per-node "Log Session" option is ignored.',
},

In the node execution logic:

const credentials = await this.getCredentials('browserbaseApi');
const browserSettings = {
    recordSession: credentials.disableSessionRecording
        ? false
        : (browserOptions.recordSession ?? true),
    logSession: credentials.disableSessionLogging
        ? false
        : (browserOptions.logSession ?? true),
    // ...
};

Why credential-level?

• Admin control: In n8n, credentials are typically managed by admins/owners — regular workflow creators use shared credentials without editing them.
• Organization-wide enforcement: A single credential shared across multiple workflows applies the policy uniformly.
• No breaking changes: Defaults to false, preserving existing behavior for all current users.
• Works on n8n Cloud and self-hosted: No dependency on environment variables or instance-level settings.

Alternatives considered

Context

We operate n8n Cloud for back-office automation (CS, Finance, HR departments) and encountered this issue when evaluating Browserbase for internal workflows. We're happy to submit a PR implementing this change if the approach is acceptable.