Improve get jobs and get job logic with new search parameters

[paaragon]

Summary

This PR adds the new jobs and provider_jobs parameters in the client:

• status
• created_after
• function_name (only for jobs)

And in the backend the changes applied are:

• Migrated /jobs and /jobs/provider endpoints to new architecture
• Added new filters: status, function and created_after date
• Added tests to cover new filters
• Added a new ProgramSummarySerializer so we return less info about the program in the job lists

Details and comments

After trying multiple solutions, I think the best pattern is to return a QuerySet in the repository but not propagate it to the endpoint. The use-case should return a business object, not the QuerySet.

I created the create_paginated_response utility method that should be used in future endpoints to maintain consistency between responses.

Also, the previous response was returning different response types. I removed the non-paginated response because it wasn't being used in the client.

[korgan00]

Good job! this is nice.
Since I was working in the files migration in parallel, naturally we didn't developed same solution. I have some lines to discuss.

If you have some time, take a look to the PR and review it because you probably have some comments for me :)

[korgan00]

the jobs_new folder should be renamed to jobs when we delete the jobs.py file. Then we should be able to delete also all the endpoints name properties because it will be auto-calculated

[Tansito]

I just left a couple of comments plus we need to add also in the client the same filters as we added for the jobs method.

[Tansito]

Now LGTM! Thanks @paaragon , @korgan00 !