Using an addon's settings in a fieldtype's `configFieldItems` breaks the CP since 6.11

[martyf]

Bug description

A user created an issue about one of my addons, where when you try to add it, you get JS errors in the console.

Refer to line 74 in the fieldtype config.

If that line is commented (and $configs is just an empty collection), the fieldtype loads.

I continued to debug by removing fields from the addon blueprint, and oddly when I had a single field, the fieldtype config loaded (when adding it to a blueprint, not editing the addon settings itself), and that field appeared on the blueprint field editor with none of the other standard config fields.

This error was introduced in 6.11.0. Rolling back to 6.10.0 loads the field config correctly.

How to reproduce

1. Install Statamic 6.11 or 6.12
2. Install the TinyMCE Cloud addon
3. Try to add the field to a Blueprint: see the JS errors in the console, and a blank screen
4. Rollback to 6.10
5. Try to add the field to a Blueprint: adds correctly

On 6.11/6.12, comment out the line 74 noted above, and the field config loads. It is something to do with loading addon settings that is causing this.

Logs

Environment

Environment
Laravel Version: 12.56.0
PHP Version: 8.4.19
Composer Version: 2.9.5
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 1
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.11.0 PRO

Statamic Addons
mitydigital/statamic-tinymce-cloud: dev-main

Installation

Fresh statamic/statamic site via CLI

Additional details

No response