Upgrade ticket format from V0 to V1 to use UUIDs

This is a necessary upgrade to deal with the fact that incremental ids
do not work in distributed systems. For instance say we have two
branches from the same commit on master and they both add a new ticket.
Both will have the same incremental ID despite being completely separate
tickets. In this case we want to use UUIDs, specifically version 1 as
defined in IETF RFC 4122. This version of UUID uses a timestamp to
generate it and as a result the UUID it generates is *sortable*. This
means that the UUIDs can be created whenever on any branch, be unique,
and will be sortable by time. No matter when or where our tickets can be
sorted correctly by this UUID in a deterministic order.

Since we are also upgrading the code we've set up migration upgrade code
to handle this in case we need to do this again in the future. We also
add a few more fields and make some breaking changes since we already
are for the UUIDs.

Resources:
- https://tools.ietf.org/html/rfc4122

4 files changed, 16 insertions, 4 deletions

diff --git a/.dev-suite/ticket/closed/3-create-a-find_root-function.toml b/.dev-suite/ticket/closed/create-a-find_root-function.toml
index 5057356..49a550c 100644
--- a/.dev-suite/ticket/closed/3-create-a-find_root-function.toml
+++ b/.dev-suite/ticket/closed/create-a-find_root-function.toml
@@ -1,6 +1,7 @@
 title = 'Create a find_root function'
 status = 'Closed'
-number = 3
+id = '0f37b780-1553-11ea-8003-000502040903'
+assignees = []
 description = '''
 One of the issues with ticket is that it has a bug in init where if it's
 not given the path to the root of a git then it will fail. This is
@@ -10,3 +11,5 @@ a more generalized function and be shared amongst future tools as this
 will be a common operation. It shouldn't matter where in a repo you are,
 the tools should just work.
 '''
+comments = []
+version = 'V1'
diff --git a/.dev-suite/ticket/closed/4-create-a-tui-for-ticket.toml b/.dev-suite/ticket/closed/create-a-tui-for-ticket.toml
index 2d4b77a..999e3c9 100644
--- a/.dev-suite/ticket/closed/4-create-a-tui-for-ticket.toml
+++ b/.dev-suite/ticket/closed/create-a-tui-for-ticket.toml
@@ -1,6 +1,7 @@
 title = 'Create a tui for ticket'
 status = 'Closed'
-number = 4
+id = '0fd04e00-1553-11ea-8004-000502040903'
+assignees = []
 description = '''
 Currently ticket is all cli driven. The experience isn't the worst, but
 the end goal has always been to get the user to be able to have a nice
@@ -8,3 +9,5 @@ in terminal experience, almost as if they never left GitHub. A basic
 tui that allows one to read and comment on issues will suffice to close
 this ticket.
 '''
+comments = []
+version = 'V1'
diff --git a/.dev-suite/ticket/closed/2-create-git-hooks-tool.toml b/.dev-suite/ticket/closed/create-git-hooks-tool.toml
index c51799c..4b929d9 100644
--- a/.dev-suite/ticket/closed/2-create-git-hooks-tool.toml
+++ b/.dev-suite/ticket/closed/create-git-hooks-tool.toml
@@ -1,6 +1,7 @@
 title = 'Create git hooks tool'
 status = 'Closed'
-number = 2
+id = '0e068a80-1553-11ea-8002-000502040903'
+assignees = []
 description = '''
 Git hooks are great, but the problem is that it's hard to standardize
 them across a team. This is because they don't travel with the repo for
@@ -9,3 +10,5 @@ repo is a good thing to standardizing checks across a team to avoid
 issues that just get caught in CI way later when it would be trivial to
 catch with a script.
 '''
+comments = []
+version = 'V1'
diff --git a/.dev-suite/ticket/open/1-add-ability-to-edit-tickets.toml b/.dev-suite/ticket/open/add-ability-to-edit-tickets.toml
index e0279d3..d668b68 100644
--- a/.dev-suite/ticket/open/1-add-ability-to-edit-tickets.toml
+++ b/.dev-suite/ticket/open/add-ability-to-edit-tickets.toml
@@ -1,9 +1,12 @@
 title = 'Add ability to edit tickets'
 status = 'Open'
-number = 1
+id = '0d6df400-1553-11ea-8001-000502040903'
+assignees = []
 description = '''
 Currently if you want to edit a ticket you need to directly edit it
 inside of the git repo itself. While it works it's hardly ideal. The
 ability to edit tickets by specifiying the id with an accompanying cli
 arg to go with it would be enough to close this.
 '''
+comments = []
+version = 'V1'