VCS Project structure

[rolsonquadras]

Here is the proposed VCS Repo structure proposal based on discussion between @aholovko @vkubiv @sudeshrshetty @DRK3 and @rolsonquadras

• Use OpenAPI as the source of truth -> easy to document and share; build Golang stubs for rest controller.
• Split code into 3 layers - rest controller, service (business logic) and database
• Use VCS-specific database packages (not Aries DB providers) - initially support MongoDB v4 APIs to support AWS DocumentDB; add new DB implementation based on requirements later.
• DB Upgradability - bundle database schema (if required), db indexing, and migration scripts outside the application

[rolsonquadras]

• Use OpenAPI as the source of truth -> easy to document and share; build Golang stubs for rest controller.

Added as part of https://github.com/trustbloc/vcs/pull/772/files#diff-6c08e65eef0374988297d041bd50f87b385613a7e478c3812cb5312cc3e1f1e3

• Split code into 3 layers - rest controller, service (business logic) and database

Added as part of https://github.com/trustbloc/vcs/pull/767/files

• Use VCS-specific database packages (not Aries DB providers) - initially support MongoDB v4 APIs to support AWS DocumentDB; add new DB implementation based on requirements later.

Updated aries as part of https://github.com/trustbloc/vcs/pull/758/files. The new KMS store implementation will be part of Issuer management profile.

• DB Upgradability - bundle database schema (if required), db indexing, and migration scripts outside the application

Created a separate issue #774