ScopeChangeRequest should be handled by ElasticSearch

[maxceem]

After we moved to "v5" standard all the endpoints should get data from ES and also store it in ES additionally to DB.

For the ScopeChangeRequest model and related endpoints we should do the next:

• GET /v5/projects/:projectId(\\d+)/scopeChangeRequests endpoint should get data from ES and fallback to DB if not found in ES as other endpoints as per "v5" standard.
• POST /v5/projects/:projectId(\\d+)/scopeChangeRequests/:requestId(\\d+) endpoint should fire event to Kafka so "project-processor-es" may process it. Same like other endpoints.
• project-processor-es should index ScopeChangeRequest objects inside the project object. Same as we do for project attachments, phases, invites and so on.
• Update GET /v5/projects/:projectId(\\d+) endpoint so it returns the property scopeChangeRequest inside the project object same like members and invites. This property should be returned when project data comes from ES or from DB.