Create general purpose web routes for supporting table view, edit view and create view by parameterizing the existing routes with the collectionName of the models

[asadeg02]

Description

The purpose of this task is to merge all the web routes for different models (which support the same operation [read, update, create] for database models) together by kind of parameterizing the route with the collectionName of the model.
Right now anchor provides 3 administration views on the UI supporting read, create and updates operations for every model being exposed to the server.(Anchor also supports delete operation, but delete doesn't need to have a separate view and the functionality exists as part of the table view).
Developers using anchor have to write separate routes (for 3 different views mentioned above) for every new model they add and they also have to create the UI components for read, update and create separately for each model.
The purpose is to have general purpose web routes and general UI components for read, update and create views so after exposing a new model to the server, the default table view, update and create view is supported and enabled for the model without having to write any code for it.

Current Behavior

Right now for each model, there exists a file inside web/routes directory with the same name as the models name including the web routes for edit, create and table view. we want to get rid of these routes and instead of having separate web routes for each model, write only 3 general purpose routes supporting the same functionality.

Steps

1- Create a module named anchor-web-route.js inside anchor directory which contains 3 different routes described in the table below

Route path	Route method	Purpose
/{collectionName}	Get	returning the table view template
/edit/{collectionName}/{id}	Get	returning edit view template
/create/{collectionName}	Get	returning the table view template

2- Extend the anchor model so that it stores the default values for the web routes attributes and create a routing map (similar to what exists for the api routes) as well.