Track GDK startup time in Remote development workspace

Overview

We need a baseline for an epic &12382 (closed) to track the startup time for GDK in Remote Development workspaces. This will give us the data we need to identify areas for reducing these times. We can use the telemetry feature for tracking and then display the results on the existing dashboard for monitoring.

Impacted categories

The following categories relate to this issue:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Steps to replicate (optional)

Proposal (optional)

Environment (optional)

• Operating system name: <!-- output of `uname -a` command -->
• Architecture: <!-- output of `arch` command -->
• The contents of your gdk.yml (if any)
• Ruby version: <!-- output of `ruby --version` command -->
• GDK version: <!-- output of `git rev-parse --short HEAD` command -->