To have API that can create people

[sugat009]

@apoorvapendse
Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

[apoorvapendse]

I plan to pick this up next, once #10028 is merged.
Just noting down what we discussed on 10th June's call:

1. Throw an error is the provided object's parent hierarchy isn't minified, when the parent's lineage contains anything other than an _id or _rev.
2. Optimistically assume that the lineage provided is accurate in terms of the parent ids as well the depth of the hierarchy.

Paraphrasing the reasoning behind this as @jkuester mentioned:
The reason behind staying rigid initially and keeping it simple is that we can expand cht-datasource's compatibility with other "complex-to-process" data later on, but doing that in the other direction(lenient to rigid) would introduce breaking changes.

cc @jkuester, @sugat009

[apoorvapendse]

I'd like to know how we want to model createPerson in shared-libs/cht-datasource/src/local/person.ts
Should I create a PersonQualifier that extends ContactQualifier which would be created using something like byPersonQualifier in shared-libs/cht-datasource/src/person.ts before calling createPerson in local /remote or is there some other way that is preferred?

I think the PersonQualifier would look something like this:

type PersonQualifier = ContactQualifier & Readonly<{
  parent: NormalizedParent,
  date_of_birth?: Date;
  phone?: string;
  patient_id?: string;
  sex?: string;
}>