Fix 717

[itsmerhp]

Applied changes in processFilter function to enforce read blacklist filter for below cases :

• If collection has status field and a field has been blacklisted for specific statuses, then filter by that field would avoid records having blacklisted statuses.
• If collection has status field and a field is blacklisted for all the statuses, then exception should be thrown on filter by that field.
• If collection has not status field and a field is blacklisted, then exception should be thrown on filter by that field.

[binal-7span]

@itsmerhp

Just gone through PR and found that the behavior of collection which has status field and which doesn't have status field is different.

Let's have an example.
(1) The collection which contains status field and the title field is blacklisted; returns the blank array for filter it with the title.
(2) The collection which doesn't contain the status field and the title field is blacklisted; throw the exception for filter it with the title.

So let's make it common for both scenarios. Kindly replace the exception of

Unable to access title related data

with

Invalid field title

As the user will not get field which is blacklisted for Read permission in the listing API and if still, they try to implement filter on that field, then it's not meant to give them the exception for the permission. Instead of that, we should return the exception like Invalid field. As they may or may not know that the blacklisted field exists in the collection.