Evaluate the context used for entity array aggregates

[RFSH]

In the code for handling aggregates, we're changing the context to always be compact for the entity array aggregates (and we're ignoring the app context).

This has been done as part of #756 and the following is the reason for it:

I realized that I am using the row_name/ for generating list of row-names in entity array aggregate. After a discussion, we decided to change this to always use the row_name/compact context regardless of its parent reference context.

But the way I implemented this is not limited just to the context used in row_name/<context> and it's affecting other parts of the code that use context. As the code will assume the parent context of compact and will use this context.

For instance, we're using context to figure out whether we should add links to the default row-names that are displayed for entity array aggregates (show_foreign_key_link). And in most deployments, the value of this display annotation property is false (we're turning off links in the compact/tabular views.) So the entity array aggregates won't show links even if they are used in detailed context, and you have to add "show_foreign_key_link": true to your source definition.

So should we still use row_name/compact for the row-name values? and if we do, should the context used for other parts of the function use compact or the parent compact?