Hot fix - create type `EnvironmentId` to to allow export

• create an exportable type EnvironmentId to avoid bug
• Upgrade the Go modules this package depends on

Use Capital letter in the indentifier so it can be exported

Important GOTCHA:

An identifier may be exported to permit access to it from another package. An identifier is exported if both:

• the first character of the identifier's name is a Unicode upper case letter (Unicode class "Lu"); and
• the identifier is declared in the package block or it is a field name or method name.

See this Stackoverflow post

Actual v1.0.0 release

v1.0.0 was released before merging (Duh!)

Use more descriptive names - Add a new function `NewDbConnexion`

WARNING: This update will break any repo that was depending on the previous version of this repo (version 0.x.x and earlier).

• Names should be descriptive and specific: replace generic or non-specific names.
• Add a function NewDbConnexion to simplify how we generate string to connect to a database
• Use variables STAGE in the Udomain function

Use AWS parameter store when deployed

Bug Fix:

When Lambda has been deployed it can only get the variables from the AWS Parameter store.

This makes sure that we get these variables when we need these

Misc:

• Remove the function NewBzDbConnexion for now this will be implemented at a later stage

Add new function `NewBzDbConnexion`

We have several repo that use a similar function to get the connection to the BZ database for a given Unee-T installation.

We are moving this in one central place.
We create a new function NewBzDbConnexion that can be used as a drop in replacement

More descriptive log messages

Include the name of the function in the Log message so we can debug more easily

Upgrade to Go v1.13

• Upgrade to Go v1.13
• Improve documentation and comments
• Rename function New to NewConfig: Names should always be descriptive whenever possible.
• Get all the improvements made when debugging unee-t/unit#16 into this repo.

Force use of Go v0.11.x

Go V0.12 can create panic when tests are run <-- forcing deployment to use Go v0.11.

Remove GO112MODULE

The reference to GO112MODULE is creating 2 builds, removing it.