[ZEPPELIN-6358] Add E2E tests about /#/notebook/:noteid for New UI

[dididy]

What is this PR for?

Addition and improvement of notebook-related E2E tests for New UI

---

/#/notebook/:noteId – View or edit a specific notebook
/#/notebook/:noteId/revision/:revisionId – View a specific revision of a notebook
/#/notebook/:noteId/paragraph/:paragraphId – Notebook paragraph presentation mode

PAGES.WORKSPACE.NOTEBOOK
→ src/app/pages/workspace/notebook/notebook.component

PAGES.WORKSPACE.NOTEBOOK_ACTION_BAR
→ src/app/pages/workspace/notebook/action-bar/action-bar.component

PAGES.WORKSPACE.NOTEBOOK_PARAGRAPH
→ src/app/pages/workspace/notebook/paragraph/paragraph.component

PAGES.WORKSPACE.NOTEBOOK_SIDEBAR
→ src/app/pages/workspace/notebook/sidebar/sidebar.component

PAGES.WORKSPACE.PUBLISHED_PARAGRAPH
→ src/app/pages/workspace/published/paragraph/paragraph.component

What type of PR is it?

Improvement

Todos

What is the Jira issue?

ZEPPELIN-6358

How should this be tested?

Screenshots (if appropriate)

Questions:

• Does the license files need to update? No
• Is there breaking changes for older versions? No
• Does this needs documentation? No

[tbonelee]

Could you rebase this onto master branch?

[tbonelee]

Could you take a quick pass on two areas?

1. There are places where try/catch accepts both error and non-error paths. Could we make these more explicit, either intentionally silencing with a clear rationale or failing, so we reduce false positives?
2. For browser-specific branches (e.g., notebook-keyboard-page.ts → executePlatformShortcut), could we extract that logic so the main flow reads sequentially and the differences are isolated?

[dididy]

You can see that request item 1 has been addressed in e92d5ae and item 2 in eea335a. Thank you for the thorough review.

[dididy]

It took some time to incorporate the review feedback, do incremental refactoring, and clean up the tests that were failing in CI.
I’ve opened #5128 with the common environment and utility changes. Once that PR is merged, I’ll follow up with the PRs below:

• A PR reflecting changes to existing test POMs, utils, and specs
• A PR for keyboard shortcut–related tests
• A PR for the remaining notebook-related tests
• A PR for tests related to shared modules (folder-rename, note-rename, note-toc)

Once all of those PRs are merged, we can close the current PR accordingly.