Fix missing types in schema (#127)

The new fields that were added for the most recent major version included
new types. There were no tests to cover the mapping when creating the schema
for the warehouses, so this was missed.

Add the new type mappings in and tests to make sure this doesn't
happen again.

Add Error Kind, Event Var Fields, Page Name, Page Num Events, and Pag…

…eNumDerivedEvents fields (#126)

* feat: add PageName field to hauser

* feat: add more fields

* tests: update schema_test

* fix: remove beta CWV

* remove BUILD.bazels

Adds the ability to configure a segment id (#123)

Updates the config to provide the ability to use a custom
segment ID instead of the "everyone" segment.

Build improvements (#114)

The releasing script wasn't working. This makes some
updates to the makefile to fix for installing
static checkers and other CLIs. 
This change also removes the vendor directory, which
is no longer needed due to using go modules exclusively.

Add new export fields (#104)

Adds the following fieds for all accounts:

* EventSubType
* EventPageOffset
* EventSessionOffset
* EventWebSourceFileUrl
* PageMaxScrollDepthPercent

Also added fields for accounts with Mobile Apps support:

* AppDeviceModel
* AppDeviceVendor
* AppVersion
* AppOsVersion
* AppViewName
* EventMobileSourceFile

Add request fields (#103)

Exports now include the following fields when the `EventType`
is `request`:

* `ReqUrl`: the URL for the corresponding XHR request
* `ReqMethod`: the HTTP request method for the corresponding XHR request
* `ReqStatus`: the HTTP response status code for the corresponding XHR request

Use new APIs for exports (#95)

This is significant update which migrates the existing export client from the existing APIs to the new (as of yet, undocumented) "Segment Export" APIs.

The aim is to be as backwards compatible as possible, but there are few notable changes from the existing workflow:

### Exports are not "bundled"
With the existing APIs, the exports were "bundled" into a time period that was defined in the "Data Export" settings for in the FullStory application. The new APIs do not have this restriction. Instead, the new APIs allows a specifying a time period for which to export data. However, the change here means that we no longer support "listing" exports since they are now user defined. Instead, a `StartTime` must be specified in the config if starting fresh. However, if a "sync" exists for the provided configuration, `StartTime` will simply be ignored.

The second implication of this is that the export duration must be specified in the config as well. The default value (if unspecified) is now 1 hour.

### New fields
With the new APIs a few new fields have been added:
* UserCreated: 
* EventTargetSelector
* SessionStart
* PageStart
* PagePlatform
* PageScreenWidth
* PageScreenHeight
* PageViewportWidth
* PageViewportHeight

### Special cased fields
* EventTargetSelectorTok: this will only be exported if a database already exists with this column.
* PageUserAgent: this field used to be called `PageAgent`. If a database already has this column, `PageUserAgent` will be translated to match. Otherwise, the column will be named `PageUserAgent`.