[Task]: Persist dependency map of a page in backend

[dvj1988]

The dependencyMap consumes considerable computation on the frontend. We would like to persist that in the backend for every page in an application.

For details on the signature and payload of the api calls please refer this document

Tasks

Beta Give feedback

1. Add dependencyMap in the response of Consolidated view api. (GET /api/v1/consolidated-api/view)
2. Add dependencyMap in the response of Consolidated edit api. (GET /api/v1/consolidated-api/edit)
3. New API to update the dependency map of a page. (PUT /pages/{pageId}/dependencyMap)
4. Add dependency map is the response of get page api (edit mode) (GET /api/v1/pages/{pageId})
5. Add dependency map in the response of get page api (view mode) (GET /api/v1/pages/{pageId}/view)
6. Publish api changes - Copy the dependency map of a page from unpublished to published.

[dvj1988]

cc: @rahulbarwal @rajatagrawal

[AnaghHegde]

Adding more story points due to last movement review comment which requires change in the flow.