The refactoring of the changes visibility in v2.16
had accidentally broken the super-powers given to the InternalUser
to access all changes in read-only, including querying
changes. InternalUser is the base class of the PluginUser, hence
the breakage impacted the ability for plugins to query changes
using its internal identity.
Consider the InternalUser as an exceptional case for
granting read only visibility and give back the ability to
read any change, regardless of current user.
Add the missing use-case to the change query visibility
tests so that InternalUser won't risk to break anymore
in the future.
Bug: Issue 12747
Change-Id: Ic6901eb2561ec15eb51aa98decbfc99eaa939f0a
20d8b49789