Implement embedded storage backend reader and writer - Part 1

[andream16]

Preparing to finish up the implementation with SQLite by:

• setting up things for SQLite in term of dependencies
• support reading the supplied workflow_id from the environment and leverage it for storing purposes in Read, Update and Write. We need such ID to connect the dots when writing and updating findings in the DB.

---

We agreed with @ptzianos to leverage the workflow_id from env var for now. We can cover the instance_id separately :)

---

I added a reusable uuid package which wraps google's UUID. Why? Because we're in charge of swapping the implementation and the interfaces don't have 3rd party dependencies.

---

What did I do?

• Added SQLite and sample TO BE IMPLEMENTED code
• Added reusable UUID package
• Passing workflow_id around where needed - also to be tracked in logs
• Refreshed examples, runners and tests to use the workflow_id

---

In the next PR

• Implement SQLite layer
• Write integration tests for SQLite layer

[coveralls]

Pull Request Test Coverage Report for Build 11598873281

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 41.631%

---

Totals
Change from base Build 11572665249:	0.0%
Covered Lines:	3375
Relevant Lines:	8107

---

💛 - Coveralls