When polling is enabled, Mesh gets the old schema on each server start

[ardatan]

When user enables the polling with pollingInterval configuration option, Mesh pulls the schema in a certain interval. It updates the artifacts automatically on the disk. But if there is a container environment or a lambda, all the changes on the disk are gone. So after a restart on the container, it starts with the initial schema that is generated via mesh build before all the following polls. Then the user gets the updated schema until the first poll. We should add a flag that immediately pulls the schema on each start so the initial artifacts are ignored.