Feature/set map support for logging

[james-ha-bruno]

Description

This PR improves the display of JavaScript Map and Set objects in Bruno's developer console to match Postman's cleaner, more user-friendly implementation.

Changes

Map Display Improvements

• ✅ Removed [[Map]] wrapper property
• ✅ Display Map entries directly at top level with => notation (e.g., "key =>": "value")
• ✅ Removed size property from display
• ✅ Added "Map" type label for clarity
• ✅ Collapse by default for cleaner console output

Set Display Improvements

• ✅ Removed [[Set]] wrapper property
• ✅ Display Set values directly at top level with numeric indices (0, 1, 2, ...)
• ✅ Removed size property from display
• ✅ Added "Set" type label for clarity
• ✅ Collapse by default for cleaner console output

Implementation Details

Modified Function: transformBrunoTypes()

• Enhanced to support metadata tracking via optional returnMetadata parameter
• Returns { data, metadata } when metadata is requested
• Metadata includes type information ('Map', 'Set', etc.)

Modified Function: formatMessage()

• Uses metadata to determine display name and collapse behavior
• Sets name prop to 'Map' or 'Set' for type identification
• Sets collapsed prop to true for Maps and Sets (collapse by default)
• Maintains collapsed={1} for regular objects (collapse at depth 1)

Testing

Tested with post-response script logging Set and Map objects:

• ✅ Sets display with numeric indices at top level
• ✅ Maps display with => notation at top level
• ✅ Both collapse by default
• ✅ Type labels clearly identify object types
• ✅ Expandable/collapsible UI works correctly

Demo

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• I have added screenshots or gifs to help explain the change if applicable.
• I have read the contribution guidelines.
• Create an issue and link to the pull request.
• Sets/Maps cannot be logged in the Bruno console; they print as empty objects. #6040

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.