core: Upgrade should set SEQUENCE number to the correct value

Table sequences may get out of sync after database is restored.
We had that in  a customer database, the sequence value for generating
option_id for vdc_options was 238 while the max(option_id) was 399. That
resulted of course with PK violation.

for more details , see:
http://www.postgresql.org/docs/8.4/static/sql-createsequence.html

Change-Id: Icd774770cbdbf197736a547de901826bdbec7abc
Signed-off-by: Eli Mesika <emesika@redhat.com>
Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=896552