Prevent duplicate articles_courses rows.

[gabina]

What is happening?

While we're using sidekiq-unique-jobs gem to add unique constraints to sidekiq jobs, and we currently set sidekiq_options lock: :until_executed in CourseDataUpdateWorker worker to avoid duplicate jobs (with the same arguments and job class), it's still possible to end up with duplicate articles_courses rows.
One possible scenario for this is when running a manual update course stats process through the manual_update route. As this update runs synchronously there is no guarantee that a queued UpdateCourseStats job will run simultaneously.

To Reproduce

Steps to reproduce the behavior:
As the problem is related to a race condition, it's not trivial to reproduce. However, this is one scenario that may show the problem:

1. Start the app locally.
2. Be sure sidekiq is up (bundle exec sidekiq start).
3. Download a course locally (you can do this through the "Copy course from another server" admin view).
4. Add the course to default campaign.
5. Run a manual update using the manual_update route (you need to be an admin for that).

If an update for that course was scheduled and run at the same time than your synchronous update, then duplicate articles_courses rows may be created.

Expected behavior

We should avoid having duplicate articles_courses rows (i.e., multiple rows with the same course_id and article_id). This can be prevented by adding a unique constraint on (course_id, article_id) in the articles_courses table. Proper tests should be done before migrating articles_courses table.

[cr3ativ3cod3r]

I am working on this issue

[ragesoss]

@cr3ativ3cod3r this is probably not a great issue for a new contributor, as it will require some manual testing against a realistically-sized database in a production-like environment.