I2I: Trinity Audio Player extension

# Summary
Trinity Audio proposes a component to enable publishers to audiofy their content using our cloud-hosted audio player.
To use the component, it is required to have an account with Trinity Audio. Registration is through our site (https://trinityaudio.ai/)

# Design document

https://docs.google.com/document/d/1TAGQQiWfP1eMDQQTKfngddghLX4b7kQkSBtbRf2RYR4/edit?usp=sharing

# Motivation

Trinity Audio allows textual content creators the option to distribute and interact with their readers using audio.
By doing so, it allows users to enjoy the high quality content they are already consuming in times when they couldn't before. As many of our publishers use AMP for their mobile content, creating an AMP component will allow them easy integration.
Using a native AMP component enables the component to trigger Analytics events so that publishers can track user interactions with the player. These events can then be collected by an `amp-analytics` component which sends it to the publisher’s analytics platform of choice.

The issue names no repository file or test. Start with the linked Google design document and the AMP component integration requirements; done means a native AMP component exists for Trinity Audio’s hosted player and emits analytics events that amp-analytics can collect.

Written by the indexing model from the issue text.