tree b85e29a42c4acc758c102ade44b64051f82c0c90
parent 7473bb0aab8869b068b913749c946c82808578ba
author Jacek Centkowski <geminica.programs@gmail.com> 1729408572 +0200
committer Jacek Centkowski <geminica.programs@gmail.com> 1730645681 +0100

Introduce the skeleton of UI for file owners status display

This is the initial change that introduces the base building blocks for
UI that will be responsible for showing (to the change owner) which file
needs to be reviewed from whom. At present it:
* hooks into the change details screen's Files section (for table header
  and each row)
* determines if user is logged (logs to console value of `hidden`,
  `userRole`, `path` and `oldPath` properties)
* introduces base building blocks for UI components (heavily inspired by
  the `code-owners` plugin UI) namely: common UI component that is
  shared between column header and content controls, thin owners model
  that is loaded reactively through the loader using a dedicated service
  (that finally calls `RestPluginApi`)
* owners service and `shouldHide` function are covered with karma basic
  unit tests
* integrates the UI part with an `owners` plugin build and resources
  (offered as `static` resource by introduction of `HttpModule`)

Note that:
* UI tests can be called from gerrit in-tree build with

    bazel test //plugins/owners/web:karma_test

* linter can be called from gerrit in-tree build with:

    node_modules/eslint/bin/eslint.js --ext .html,.ts --fix plugins/owners/web

Bug: Issue 373151160
Change-Id: I529d1345528da0322bee2c360241935a8b4379e6