Upgrade Task Build 602 leaves the Membership sequence in an inconsistent state

Upgrade Task Build 602 updates the "Membership" sequence used by the new "cwd_membership" table

in line 284

updateSequence(connection, "Membership", "cwd_membership");

at the end of the migrateUsers method.

This is wrong as we haven't migrated the memberships to the new table yet, this call should have really been done at the end of the migrate memberships method.

Currently we will leave the value of the "Membership" at 10, as we add more memberships the value generated by the sequence will collide with the rows produced by membership migration turning into a primary key constraint violation.

This will prevent more memberships from being added to JIRA.

The workaround to the problem will be manually update the sequence using SQL so that the value of the sequence equals select max(id) from cwd_membership + 1