Update with upstream changes from XLSForm/pyxform

[jkuester]

This fork of https://github.com/XLSForm/pyxform is many years out of date.

Updating to the latest version of pyxform would give the following benefits:

• DETERMINISTIC ORDERING OF XML ATTRIBUTES
  • This is the most important change as currently, regenerating a form xml that has not changed can still result in a significant diff since the ordering of attributes in the xml elements is not deterministic and their order can change (even if the content of the xlsx file stayed the same).
• Access to the latest ODK spec features and new fixes in pyxform

The https://github.com/medic/pyxform/tree/uplift_to_v1.10.0 branch has a proof-of-concept upgrade to version 1.10.0 of XLSFORM/pyxform. I was able to successfully convert this form using a slightly modified version of cht-conf. Then I was able to successfully submit the default delivery form using both the new version of Enekto in CHT 4.0.0 and also the old version of Enketo in 3.x.

Thoughts:

• Seem to be getting a new warning printed when converting xlsx files that contain cell validation. I think we could include -W ignore:"Data Validation extension is not supported" in our xls2xform-medic call somehow to suppress the warning.
• label elements are still getting added to the body even for empty labels. This might be intentional (as part of the spec). Or, it might be because I did not add the custom label code to my uplift_to_v1.10.0.
  • No warning unlabeled group 2 XLSForm/pyxform#545
  • Output empty <label/> instead of omitting it. XLSForm/pyxform#543
  • Output empty <label/> instead of omitting it. XLSForm/pyxform#439
  • This will cause display issues in app (may need webapp change?)
    • 
• pyxform no longer likes the way that we only include the language tag (e.g. label::en) in our translatable column instead of following the spec and putting label::English (en)
  • Continuing to just put the tag seems to still work fine, but does cause a warning to be printed.
  • But, updating to the proper spec format could require changes in cht-core to support?
    • Support full Xlsform Spec label translations in forms cht-core#7589
    • https://forum.communityhealthtoolkit.org/t/issues-with-translations-of-forms/1839
• I have kept the custom code in uplift_to_v1.10.0 to support copying instance::tag values, but we may want to find a better way to do this since it seems like this is out of spec
• Also, more investigation is needed to know if we need out custom SMS code in pyxform still or if the added support is sufficient.

[jkuester]

Once this issue has been resolved, medic/cht-core#6537 should be evaluated to make sure we can move cht-core and cht-conf to Python3.

[mrjones-plip]

Noting the nondeterministic ordering of XML attributes really messes up the sha256 hashes we include :( This was uncovered in a recent forum thread.