Migrate to Oori Data and reclaim the amara PyPI project

[uogbuji]

The Amara saga continues! I don't exactly remember why I decided to dead end the Amara PyPI project when it hit 2.0, but I moved to a series of Amara 3 generation projects (amara3.iri, amara3.xml & amara3-names). Those were far more lone wolf efforts, but at Oori Data we're seeing a lot of need for the sorts of capability that's inchoate in Amara 3.

Time to re-consolidate the Amara projects, call it a 4th generation, and move it to Oori Data GitHub.

• Create https://github.com/OoriData/Amara project
• Prepare its initial codebase from https://github.com/uogbuji/amara3-iri & https://github.com/uogbuji/amara3-xml project
• Release to https://pypi.org/project/Amara/ as 4.0.0a1 (counting up via 4.0.0a2…4.0.0a9…4.0.0a10……4.0.0b1……4.0.0rc1, and so on). I picked this designation after far too much pondering of SemVer and PEP 440 considerations (e.g. this)
• Archive the https://github.com/uogbuji/amara3-iri, https://github.com/uogbuji/amara3-xml & https://pypi.org/project/amara3.xml/ (latter probably doesn't have much worth saving) in GitHub
• Add deprecation notes to relevant PyPI projects (note: there seems no formal metadata approach for this yet)
  • amara3.xml
  • amara3.iri
  • pybibframe
  • datachef
  • Akara
  • wsgixml
  • 4Suite-XML
  • Amara-XML-Toolkit
  • Anobind

Note: Pip & PyPI are case insensitive. PEP 426 says All comparisons of distribution names MUST be case insensitive, and MUST consider hyphens and underscores to be equivalent. An amara 4.0.0a1 package will seamlessly supersede Amara 2.0.0