Reconsider when EF schema migrations are applied

[adityamandaleeka]

From @bricelam

Today, database schema migrations are applied as certain components start up. This is problematic when multiple components (or multiple instances of the same component) use the same database.

Currently, for example, Ordering.BackgroundTasks immediately begins querying the OrderingDB database. This continually fails while waiting for Ordering.API to create and migrate the database schema to the latest version.

Data seeding (#10) should also be done at the same time.

[AndriySvyryd]

WaitForResourceAsync(...) can be used to fix this once implemented.