Expose custom remote methods contributed by CRUD connectors on top of DAO methods

[bajtos]

In #2036, we build infrastructure for exposing CRUD/KeyValue models via REST API with no intermediate repositories and controllers. In that first step, only the default CRUD or KeyValue API will be exposed.

In LB3, connectors can contribute additional remote methods on top of the default DataAccessObject API. Let's find out how to expose these additional methods too.

This story depends on the outcome of #2481 and implementation of subsequent stories.

Related: #2481

[bajtos]

Based on my recent discussion with the AppConnect team, they may take a different approach to redesigning their project for LB4, in which case this feature won't be needed (by them).

Let's remove it from our near-term backlog.

[stale]

This issue has been marked stale because it has not seen activity within six months. 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. This issue will be closed within 30 days of being stale.

[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.