Labware v2: deprecate all uses of 'format'

[IanLondon]

overview

(discussed on Slack)

Labware format is something we’ll treat as unimportant once APIv2 is out, and we can deprecate uses of that field, so it’s fine to always be "irregular" which means “don’t assume anything about this labware from the format field”.

Currently, format is used:

• in APIv1 (api/src/opentrons/legacy_api/containers/__init__.py) to make special weird geometry compensations for rectangular wells
• in PD, getDisposalLabwareOptions selects only format === 'trash' labware. But we don’t have any format: "trash" definitions that you can add to the deck, so it’s not very useful to do that.
• shared-data helper fn canPipetteUseLabware uses format to determine if labware can be used by multi-channel. All it really does is that for format: "irregular" definitions, it returns false and returns true for everything else. This fn is used a few places in PD, we could change it to use geometry to determine if tips will fit (this geometry logic already exists in PD and is used for liquid tracking updates)

Those places will need to be changed to avoid using the format field.

The format key is part of the v2 labware def schema, but we can as a convention set it to irregular for new labware defs, and otherwise ignore it. In the next labware def schema v3, we could drop the format field altogether; the behaviors it’s supposed to control can be captured in quirks.