Notedb: Fix wrong patch set id on upload new patch set

ReceiveCommit with notedb enabled site uses erroneously old patch set
id in ChangeUpdate on upload of new patch set. This bug was hidden
because no tests were enabled that targeting Notedb backend during push
operation. Fix this by enabling standard push tests also for Notedb
configuration.

Test Plan: When approval provided during push operation by passing
-l parameter to magic branch, verify that the approval is referencing
the right patch set. That means, pushing a change with %l=Code-Review+1
and uploading a subsequent patch set with %l=Code-Review+2 produces the
following commits on meta branch:

Uploaded patch set 1.

Patch-set: 1
Label: Code-Review=+1

Uploaded patch set 2.

Patch-set: 2
Label: Code-Review=+2

Without this change the last two lines are:

Patch-set: 1
Label: Code-Review=+2

and as result the test: testPushForMasterWithApprovals() was failing
because CRVW+2 was referencing wrong patch set (1 instead of 2).

Change-Id: I231e736a3d5f44555b1c2e4bdb5ef43be035c624