Replace filter implementation with loopback-filters

[bajtos]

Let's deliver the promise we made in our [docs] long time ago:

We plan to convert all modules to use loopback-filter, so it will become LoopBack’s common “built-in” filtering mechanism.

Right now, loopback-filters are always behind the "real" loopback implementations and people have to port new features from loopback-datasource-juggler to loopback-filters to keep them up to date (see e.g. strongloop/loopback-filters#13, strongloop/loopback-filters#10, strongloop/loopback-filters#3, strongloop/loopback-filters#20).

Once we switch juggler to use loopback-filters, there will be only a single place where to add new filtering features.

Important note: this change should be fully backwards compatible, all existing tests in loopback-datasource-juggler and loopback should keep passing. This will most likely require improvements to be made in loopback-filters to get them feature parity with what we have in juggler right now.

[aatif-lahore]

Do you have updated loopback-filters?

[bajtos]

@aatifhussain I am afraid I don't understand your question, what kind of updates do you have in mind? AFAIK, no action related to this issue has been made yet.

[aatif-lahore]

@bajtos You got it right, Thank you.

[privateOmega]

@bajtos I have put in a PR 15 days ago pending review.

[bajtos]

@privateOmega thank you for pinging me, I reviewed your strongloop/loopback-filters#26 and left some comments, PTAL.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dhmlau]

not stale. PR in review.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.