DATAUP-461 Refactor Retry

[bio-boris]

Description of PR purpose/changes

Summary: In order to ensure DB consistency, we need to rework the retry mechanism

Remove retry_count field from record
Add retry_ids field to record
Change check_job/check_jobs to return “retry_count” in addition to “retry_ids”
Change retry to return “retry_ids”
Add a toggle field to ensure database is consistent in terms of updating the parent_retry and parent_job_id  

Testing Instructions

• Deployed on CI
• Delete all records with retries in CI db, and prod db.

db.getCollection('ee2_jobs').update({'retry_count' : { $exists: true }}, { $set: {"retry_ids": [] }}, {upsert:false,
                          multi:true})  

db.getCollection('ee2_jobs').update({'retry_count' : { $exists: true }}, { $unset: {"retry_count" : ""}}, {upsert:false,
                          multi:true})  

db.getCollection('ee2_jobs').find({'retry_count' : { $exists: true }})

Dev Checklist:

• [x] My code follows the guidelines at https://sites.google.com/truss.works/kbasetruss/data-upload-project/development
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules
• [x] I have run Black and Flake8 on changed Python Code manually or with git precommit (and the Github Actions build passes)

Updating Version and Release Notes (if applicable)

• [ ] Version has been bumped for each release
• [ ] Release notes have been updated for each release (and during the merge of feature branches)