Some interfaces interfere with TS Utility Types

[Maxim-Mazurok]

For example:

interface Record {
    /**
     * Key defines all of the unique querying parameters needed to look up a user
     * experience record.
     */
    key?: Key;
    /**
     * Metrics is the map of user experience data available for the record defined
     * in the key field. Metrics are keyed on the metric name.
     *
     * Allowed key values: ["first_contentful_paint",
     * "first_input_delay", "largest_contentful_paint",
     * "cumulative_layout_shift"]
     */
    metrics?: Record<string, Metric>;
}

is generated for gapi.client.chromeuxreport.

interface Record overrides built-in Record<K,T> which results in error Type 'Record' is not generic.

We should check that our interfaces do not override any TS specific terms/words. Utility Types are great starting point. Ideally, we should get these types list from TS dynamically instead of hardcoding.

[Maxim-Mazurok]

Actually, we can instead inline Record or any other built-in Utility Types that we use in generated typings: #206

Or, just re-define them with another name.

Downside: we're hard-coding current implementation of Record.