Add index + unique constraint on issue_id and comment_id

The current schemas for `issue` and `comment` don't have any unique constraint and index on `issue_id` and `comment_id` yet.
This can be useful to make sure the data inserted are correct and to avoid duplicates.
A duplicate values can appear for example if the app is uninstalled and reinstalled again. As we won't automatically delete data in Postgres (see #87) this means that on the install we will save again all the issues and comments (see #65)
After adding these indexes and constraints we will need to update the Repo.insert` function on new install to `Repo.insert_or_update`:
https://github.com/dwyl/github-backup/blob/2960a82e0f2d89853d86380db4e5841677bbdbf3/lib/app_web/controllers/event_type_handlers.ex#L69

see https://hexdocs.pm/ecto/Ecto.Repo.html#c:insert_or_update/2

Start with the issue and comment schemas, then inspect lib/app_web/controllers/event_type_handlers.ex around line 69 and the Ecto Repo.insert_or_update/2 documentation. Done means issue_id and comment_id have the requested indexes and unique constraints, and the new-install path updates existing records instead of inserting duplicates.

Written by the indexing model from the issue text.