introduce data connectors, used to validate if vin is allowed to connect

[patrickdemers6]

Description

Introduces the concept of data connectors which can use externally provided data to enhance server functionality.

The data connectors supported so far:

• Redis
• HTTP
• File
• gRPC

To start, data connectors are used for one capability: checking if a vin is allowed before allowing it to send data to the server. This prevents a compromised vehicle from being able to send data to a random fleet-telemetry server.

Please select all options that apply to this change:

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Bug fix (non-breaking change which fixes an issue)
• Documentation update

Checklist:

Confirm you have completed the following steps:

• My code follows the style of this project.
• I have performed a self-review of my code.
• I have made corresponding updates to the documentation.
• I have added/updated unit tests to cover my changes.
• I have added/updated integration tests to cover my changes.

Other Notes

• To generate gRPC service protos, additional dependencies are needed. The generation of protos is now handled by a Docker container.
• General dependency upgrades.
  • Ginkgo no longer supports SlowSpecThreshold so it has been removed.

[aaronpkahn]

heh, last connector wins!

[patrickdemers6]

I'd like to reject connection before web socket is established but am not having success. Getting that working can be a followup if someone wants to work on it.