Migrate denormalization data to denormalization microservice

Because we can not make the faas work, so we have to use denormalization microservice to generate the data.

Reference: https://github.com/Greenstand/treetracker-functions/issues/2

Start by reading this issue alongside the referenced treetracker-functions issue #2 to understand why FaaS is unavailable and what denormalization data must be migrated. Then inspect the repository's denormalization microservice entry points and existing data-generation workflow. Done means the required data is generated by the microservice rather than FaaS, though this issue does not define the migration scope or validation criteria.

Written by the indexing model from the issue text.