Previously, if the server did not return enabled=true for the rebase
change action, the rebase button would be disabled on the UI. Really,
what disabled indicated in this case was that the rebase could not be
performed on the current branch, but could still perform a rebase on
a different parent revision.
This change updates revision actions in the change view always be
enabled, and introduces a new parameter to indicate whether or not
rebasing should be enabled on the current branch based on the initial
status of the enabled flag.
This change also disables the rebase button on the rebase dialog until
an option is explicitly chosen. Previously, if an option was not chosen,
if rebase was clicked, it would submit with a base branch of '', which
is the same thing checking the box accomplishes. Now, either the box
must be checked, or a base change must be entered, so it is more clear
what happens with the rebase and in the new scenario when you cannot
submit on the base branch, there won't be a possibility of a server
error.
Bug: Issue 5126
Change-Id: I47083ad328095aad4e04f2fc1586ad4d34412e4c
a5056224d1