Feat/migrate get jobs endpoint

[paaragon]

• I have added the tests to cover my changes.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.

Summary

• 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

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.

[Tansito]

As we commented internally we are going to close this PR and do the review in the #1695 as it was just created with this branch as base and @korgan00 started a review there.