There were two problems with secrets related to branches. First,
a secret defined in one branch could not be used in another. This
is because the isSameProject method was a bit overzealous and also
ensured the secrets were on the same branch. Relaxing that allows
secrets to be used by jobs defined in multiple branches of the same
project.
Second, because secrets are required to be globally unique, the
expected workflow of branching a project would immediately produce
a configuration error since the secret would already be defined.
To handle this case, allow multiple definitions of a secret, but
only if they are in multiple branches of the same project, and only
if they have the same data. This should facilitate this workflow,
as well as the ability to age-out secrets on old branches.
We do not support different values for the same secret name on
different branches.
Story: 2001443
Task: 6154
Story: 2001442
Task: 6153
Change-Id: Ia9d5b77d1ce46e6461b370e951301ede4045bbb9
a17a8e7ba4