Enhancement: standardize editor panel

[adamdoe]

This pull request refactors the EditorPanel component in the chart package to use the shared EditorPanel base component from @cdc/core, and cleans up chart-specific logic. It also improves code readability and consistency in the UI, particularly in tooltip and markup formatting.

Component refactor and architecture:

• Replaces the custom EditorPanel implementation in packages/chart/src/components/EditorPanel/EditorPanel.tsx with the shared EditorPanel (BaseEditorPanel) from @cdc/core/components/EditorPanel/EditorPanel, removing the dependency on the Layout and ErrorBoundary components and updating the render logic accordingly. [1] [2]
• Moves chart-specific logic (such as convertStateToConfig) into a custom function and passes it to the base panel as needed, ensuring chart requirements (like handling newViz field) are preserved.

Code cleanup and state management:

• Removes unused state (displayPanel) and the associated onBackClick handler, simplifying the component’s state management. [1] [2]
• Removes the previous convertStateToConfig and related useEffect, centralizing the config transformation logic.

UI and markup consistency:

• Refactors tooltip and markup formatting throughout the file for improved readability, including consistent indentation for <p> tags and multi-line attributes in JSX. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]

These changes streamline the component, promote code reuse, and improve maintainability and user interface consistency.

[jayb]

This looks & works great. There's one rogue console.log for "[VisualSection] Rendering with config".

A couple questions about the new hooks in core, but these are just things to consider and you know best.

• There are still some definitions/references for getColumns sprinkled around. Should those be changed to use useDataColumns, or are they different and need to be kept?
• It looks like useListManagement is only being used in once place; are there more opportunities? If we're going to generalize it, it feels like it should be used more than once.