Feature #1 — Build A new task to assign entities in the async request processor

[eveleighoj]

Overview
We need to add an additional task to the async processor which take very similar information tot he check url but instead of simply checking the url it uses the lookup.csv and other configuration files to process the resource. It should then return the rows which do not have assigned entities as well as suggested rows to add to the lookup.csv.

Pull Request(PR):

Tech Approach

• Testing has to be implemented for all changes according to our testing guidance
• will need to identify the best way of adding a task as currently we only have one celery task but type is used to distinguish. this may not be a scaleable approach and we should check to see if we should be more aligned with the celery framework.

Acceptance Criteria/Tests

• a request can be made to the async processor which checks the rows of a resource to see if any need an entity to be assigned. The related outputs can be returned from the response & response details tables.
• This is a separate task to the current tasks and in no way should affect how they are run hence not impacting the current way the submit service uses them
• the task name should be assign entities

Tasks(to be turned into sub-issues and fleshed out)

• spike: identify methods of creating a new task and seek decision on way forward
• spike: create example endpoint returns and explain how it's stored in the postgres data model, include comparison to check url
• spike: understand any additional data requirements of the task compared to the check_url task
• create assign-entities task (big task but single PR will likely have a lot of tasks on the ticket)