feat: add elevation to shared client

[paulschreiber]

Description

Add elevation to shared client

Related issues

Backend: techmatters/terraso-backend#1286

[shrouxm]

LGTM.

should note that as is this'll be a breaking change for the mobile client due to elevation being a required field on the backend, so we shouldn't merge it until we're ready to make that associated change in the mobile client

[paulschreiber]

@shrouxm @tm-ruxandra making elevation optional broke the type checking:

  Types of property 'elevation' are incompatible.
    Type 'number | null | undefined' is not assignable to type 'number | undefined'.
      Type 'null' is not assignable to type 'number | undefined'.

I now allow elevation to be null:

  elevation?: number | null;

Is that the right fix?

[shrouxm]

yes i think so right now

it's an ongoing tech-debt issue that the client types and the backend don't quite agree, so the client right now is configured to be generous in what it accepts. eventually i'd like to make it so that it's just either elevation: Site | null or elevation?: Site, because i think there's only one case where it'd be absent, but i'm not sure which if that's the case or which one makes more sense which is why i haven't done it