Remove ===== style section headers from Dashboard

[somebody1234]

Pull Request Description

• Remove ====== section headers from Dashboard codebase

Important Notes

Let me know if some comments should be preserved as doc-style comments. This is a quick-and-dirty refactor using find-and-replace with the empty string. Search string used in VS Code included below for posterity.

(// =+)
// ===.+
\1

Note that the trailing and leading newline are important.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

[github-actions]

🧪 Storybook is successfully deployed!

📊 Dashboard:

• 👀 Review changes: https://www.chromatic.com/build?appId=673738989fc3e8430364197e&number=2071
• 👨‍🎨 Preview storybook: https://673738989fc3e8430364197e-csnhvzepva.chromatic.com/

[vitvakatu]

What is the reasoning here? I think in a lot of cases these comments help navigate big source files.

[MrFlashAccount]

Even though these comments are obsolete for Dashboard code (we prefer smaller files), I’m certain we need to discuss this with the project-view team first. Alternatively, we can scope this PR to only touch dashboard-related code.

[somebody1234]

yeah i think in project view they're used better, in the dashboard most files are on the smaller side so they're often used to annotate the single export

[farmaazon]

Yes, please spare headers in project-view files.

BTW, these are not particularly "rust specific", these are just our headers. Scala files have similar.

[somebody1234]

pinging @MrFlashAccount for CR.

QA should not be needed because there are no code changes