Entrypoint filtering for configuration and deployment APIs

[mmarchetti]

Intent

This PR adds a new entrypoint query parameter to the GET /api/configurations and GET /api/deployments endpoints. Only configurations with a matching entrypoint (or deployments whose configuration has a matching entrypoint) will be returned.

Part of #1847

Type of Change

• • Bug Fix
• • New Feature
• • Breaking Change
• • Documentation
• • Refactor
• • Tooling

Automated Tests

Added unit tests specific to the new parameter.

Directions for Reviewers

Test with curl:

$(just executable-path) ui -vv --listen=localhost:9001 &
curl -s 'localhost:9001/api/configurations?dir=test/sample-content/rmd-static-1&entrypoint=static.Rmd'|jq
curl -s 'localhost:9001/api/configurations?dir=test/sample-content/rmd-static-1&entrypoint=index.htm'|jq

[dotNomad]

This works great I just had a note about the upcoming recursive work that I was concerned about with this initial implementation. That doesn't matter quite yet though. Tested and this worked with the dir query and without.

[dotNomad]

It looks like this won't work how I expect when we add recursion. We can adjust when we add that functionality, but the way I would expect this to work is to pass the relative path to the entrypoint and not just simple.py. That way if there are multiple simple.py files in the many folders I get back the only way I care about.

[mmarchetti]

Yes, we'll need to consider that. I'll make a note in the issue for recursion (#1850).

[dotNomad]

Meant to mark this as approved