docs(app): add quick transfer doc to keep track of versioning

[smb2268]

Overview

This PR adds a versioning doc to keep track of changes in Quick Transfer. We don't currently read designerApplicationData for QT but this will enable us to do so in the future and migrate old iterations if need be.

Review requests

Does this location make sense as the place to store this information?

Risk assessment

Docs only

[jerader]

amazing! thanks for writing this up. This is unrelated but it is confusing that we have a DesignerApplicationData for pd and one for quick transfer since they vary drastically 🤔 it is probably fine though since the types are defined in different projects

[smb2268]

amazing! thanks for writing this up. This is unrelated but it is confusing that we have a DesignerApplicationData for pd and one for quick transfer since they vary drastically 🤔 it is probably fine though since the types are defined in different projects

@jerader The idea was to have the field be the same since it should serve the same purpose - both are data specific to the application the protocol was designed with that can be reabsorbed by that application. The name field can be used to determine which application it's compatible with/which TS type it is. Doesn't PD have name: opentrons/protocol-designer?

[jerader]

amazing! thanks for writing this up. This is unrelated but it is confusing that we have a DesignerApplicationData for pd and one for quick transfer since they vary drastically 🤔 it is probably fine though since the types are defined in different projects

@jerader The idea was to have the field be the same since it should serve the same purpose - both are data specific to the application the protocol was designed with that can be reabsorbed by that application. The name field can be used to determine which application it's compatible with/which TS type it is. Doesn't PD have name: opentrons/protocol-designer?

@smb2268 , oh ya it does! okay that makes sense to me 😄