OZ-541: E2E tests for the flows between O3 and ERPNext.

[kdaud]

Ticket OZ-541

This PR adds E2E tests for the flows between O3 and ERPNext;

• Ordering a lab test for an OpenMRS patient creates the corresponding ERPNext customer.
• Ordering a drug for an OpenMRS patient creates the corresponding ERPNext customer with a filled quotation.
• Ending an OpenMRS patient visit with a synced drug order updates the corresponding ERPNext draft quotation to an open state.
• Revising a synced OpenMRS drug order edits the corresponding ERPNext quotation line.
• Ordering a drug with a free text medication dosage for an OpenMRS patient creates the corresponding ERPNext customer with a filled quotation.
• Discontinuing a synced OpenMRS drug order for an ERPNext customer with a single quotation line removes the corresponding quotation.

[corneliouzbett]

I've left a fews comments but otherwise this looks good already.
Can we have a more systematic naming for the test cases e.g something like:
"Ordering a drug in system A creates quotation item in system B" or
"Ordering a drug in system A should create a quotation item in system B".

Assuming the secondary flows.

[kdaud]

Can we have a more systematic naming for the test cases e.g something like:
"Ordering a drug in system A creates quotation item in system B" or
"Ordering a drug in system A should create a quotation item in system B

We're following similar naming convention which indicates 'Actions in component A → effects in component B':

References:

• OZ-544: Renormalized test titles and file names + Updated GA to v4 #82
• https://www.notion.so/mekom/Ozone-E2E-Tests-titles-e797c18b8c2b45ea9dda2a24ffee94cc

[corneliouzbett]

Thanks @kdaud
LGTM