Remove unwanted intermediate resources When INCLUDE used to query nested field

Problem/Motivation

Follow JSON API Specification 1.0 to provide full linkage in compound documents without including potentially unwanted intermediate resources

Proposed resolution
https://jsonapi.org/format/#fetching-includes
Note: A server may choose to expose a deeply nested relationship such as comments.author as a direct relationship with an alias such as comment-authors. This would allow a client to request /articles/1?include=comment-authors instead of /articles/1?include=comments.author. By abstracting the nested relationship with an alias, the server can still provide full linkage in compound documents without including potentially unwanted intermediate resources.

Remaining tasks

User interface changes

API changes

Data model changes