[B4B] Adapt Side Panel to support merge view of bookmarks

Prior to this CL:
- The side panel relied on getting the bookmark list shown from the
public extensions API though: `chrome.bookmarks.getTree()`.
- Most of the code in the Side panel relies on the extensions
structure `chrome.bookmarks.BookmarkTreeNode`.

The Side Panel is expected to show a merged view of the permanent
folders; e.g. BookmarksBar folder and Managed Bookmarks should be
shown as one folder containing all the nodes from both the account
and local bookmark folder. Similarly `Other` (all bookmarks) and
`Mobile` nodes should behave the same, even though those are flattened
in the side panel view.

To approach that; this CL introduces a new way to provide the
bookmarks to the side panel using `BookmarkMergedSurfaceService`:
- Adds a new handler function to retrieve the all current combined
permanent folders.
- Adds a `BookmarksTreeNode` Mojo type that maps to the existing
extension object, with the same needed elements.
- On the Ui side, a helper function allows to transform the Mojo
object to the extension object - this is needed for now to avoid
having huge mechanical changes (TODO added to investigate the need
to change all usages to Mojo element instead).

Changes in tests are only to adapt to the new function, no behavior
change is expected.
Added further unit tests for the handler.

Bug: b:380806881
Change-Id: Idfb85b3f866f07c8f521ce7568767983e97c4e22
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6239895
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Emily Shack <emshack@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Alison Gale <agale@chromium.org>
Commit-Queue: Ryan Sultanem <rsult@google.com>
Cr-Commit-Position: refs/heads/main@{#1442177}
18 files changed
tree: 7234a7026a221499328fa359eaf037ac695ec51a
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.