Bring in calitp-data-analysis and remove calitp-data

[atvaccaro]

Description

Describe your changes and why you're making them. Please include the context, motivation, and relevant dependencies.

Should merge #2837 first and rebase this one.

Brings calitp-data-analysis here and completely removes dependencies on calitp-data. Migrates any references/updates all images.

Every time I do this, it makes me think we should combine some images. :)

TODO: could be a follow-up PR, but still need to set up publishing to pypi for the 3 packages (map utils, data infra, data analysis)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

How has this been tested?

Include commands/logs/screenshots as relevant.

CI is running mypy and tests. I've testing the archiver, Airflow, and pod operators.

TODO: test jupyter

Post-merge follow-ups

Document any actions that must be taken post-merge to deploy or otherwise implement the changes in this PR (for example, running a full refresh of some incremental model in dbt). If these actions will take more than a few hours after the merge or if they will be completed by someone other than the PR author, please create a dedicated follow-up issue and link it here to track resolution.

• No action required
• Actions required (specified below)
  Deploy new Jupyter pipeline images. Run stuff in production. Mark calitp-py repo as deprecated.

[github-actions]

Preview url: https://data-infra-2838--embeddable-maps-calitp-org.netlify.app

[SorenSpicknall]

Approving, with one question: what's the separation rationale behind removing the get_fs call from __init__.py in calitp_map_utils? Just trying to reduce dependencies that stretch across different parts of the ecosystem?

[atvaccaro]

Approving, with one question: what's the separation rationale behind removing the get_fs call from __init__.py in calitp_map_utils? Just trying to reduce dependencies that stretch across different parts of the ecosystem?

Right exactly, the original calitp-py became a dumping ground for shared code as I split up/created jobs. Now I'm trying to rectify that by limiting the chain of dependencies, even if that means copy-pasting (relatively small) pieces of code that don't really need to be a packaged function anyways.