Repository: payloadcms/payload (ts)

Issue:
Lable improperly rendered for collapsible sub-fields in bulkEdit view
### Link to reproduction

https://github.com/wrobson-lllow/payload/tree/wr-collapsibleField-bulkEdit-label

### Describe the Bug

According to the docs, Collapsible fields should be presentational only.  However, when using the editMany/bulkEdit feature of a collections list view fields contained within a Collapsible are being displayed as if they were nested (like how a group field is displayed/labeled) i.e. `{collapsible label} > {innerField label}`. While this on it's own is not a huge issue on it's own the main issue is when using a function for the label definition in the [collapsible's field config](https://payloadcms.com/docs/v2/fields/collapsible). 

```
 {
      type: 'collapsible',
      label: 'Collapsible One',
      fields: [
        {
          name: 'textField',
          type: 'text',
        },
      ],
    },
    {
      type: 'collapsible',
      label: ({ data }) => `Collapsible Two - ${data.selectField}`,
      fields: [
        {
          name: 'selectField',
          type: 'select',
          options: ['A', 'B', 'C'],
        },
      ],
    },
```

These two fields are rendered as shown in the screenshot below:

![Image](https://github.com/user-attachments/assets/d2a064ba-1487-44c6-b67e-d3e1985a4401)


### To Reproduce

In the included Reproduction repo:

- Start Project  with `pnpm dev _community`
- Navigate to admin panel
- Create a new record in the "Examples" collection
- Return to list view of "Examples" collection
- Select a record and click "Edit"
- Open the "Select a value" menu

### Payload Version

2.32.0

### Adapters and Plugins

_No response_

Pull request:
fix: remove collapsible label prefix from the FieldSelect dropdown component
### What?

Removes Collapsible label from child field label in the `FieldSelect` component (for example Bulk Edit field select dropdown)

### Why?

Including the Collapsible field label in the option label of the FieldSelect component could potentially be confusing to a user as it eludes to the field being nested in the Data schema.

### How?

In the reduceFields function of the FieldsLabel component, if  `field.type === 'collpasible'` the collapsible field's label will not be combined with the child fields labels. 

Fixes #10757 

Patch:
diff --git a/packages/payload/src/admin/components/elements/FieldSelect/index.tsx b/packages/payload/src/admin/components/elements/FieldSelect/index.tsx
index 512a3b4b5c..bf3c05c88b 100644
--- a/packages/payload/src/admin/components/elements/FieldSelect/index.tsx
+++ b/packages/payload/src/admin/components/elements/FieldSelect/index.tsx
@@ -38,6 +38,9 @@ const reduceFields = (
     ) {
       return fieldsToUse
     }
+    if (field.type === 'collapsible') {
+      return [...fieldsToUse, ...reduceFields(field.fields, i18n, path, labelPrefix)]
+    }
     if (!(field.type === 'array' || field.type === 'blocks') && fieldHasSubFields(field)) {
       return [
         ...fieldsToUse,


Test patch:
diff --git a/test/fields/e2e.spec.ts b/test/fields/e2e.spec.ts
index 47de77f8e8..ecc7e72563 100644
--- a/test/fields/e2e.spec.ts
+++ b/test/fields/e2e.spec.ts
@@ -612,6 +612,20 @@ describe('fields', () => {
       )
       await expect(customCollapsibleLabel).toHaveCSS('text-transform', 'uppercase')
     })
+
+    test('should not render collapsible label in bulk update field select', async () => {
+      await page.goto(url.list)
+
+      await page.locator('input#select-all').check()
+      await page.locator('.edit-many__toggle').click()
+      await page.locator('.field-select .rs__control').click()
+
+      const firstCollapsibleOption = page.locator('.rs__option', {
+        hasText: exactText('Text'),
+      })
+
+      await expect(firstCollapsibleOption).toBeVisible()
+    })
   })
 
   describe('blocks', () => {