Delete old version of GTFS-RT parse code (#4391)

* Delete old version of GTFS-RT parse code

* Remove build package workflow and references to old version of gtfs_rt_parser_v2 on jobs folder.

[#4382]

Author: erikamov

.github/workflows/build-gtfs-rt-parser-v2-image.yml

@@ -12,6 +12,5 @@ READMEs describing the individual testing and publication process for each image
 | calitp-data-infra       | Shared imports and tools used by data infrastructure and data pipelines within the Cal-ITP ecosystem                                  | https://github.com/cal-itp/data-infra/tree/main/packages/calitp-data-infra                       | https://github.com/cal-itp/data-infra/tree/main/packages/calitp-data-infra    | https://test.pypi.org/project/calitp-data-infra            | Python Package |
 | dask                    | Parallelization infrastructure used by JupyerHub                                                                                      | https://github.com/cal-itp/data-infra/tree/main/images/dask                                      | https://github.com/cal-itp/data-infra/tree/main/images/dask                   | https://ghcr.io/cal-itp/data-infra/dask                    | Docker Image   |
 | gtfs-rt-archiver-v3     | Underpins our GTFS-RT archiver service, allowing us to save fast-moving GTFS-RT data                                                  | https://github.com/cal-itp/data-infra/tree/main/services/gtfs-rt-archiver-v3/gtfs_rt_archiver_v3 | https://github.com/cal-itp/data-infra/tree/main/services/gtfs-rt-archiver-v3  | https://ghcr.io/cal-itp/data-infra/gtfs-rt-archiver-v3     | Docker Image   |
-| gtfs-rt-parser-v2       | Code to parse GTFS RT protobufs into newline-delimited JSON for querying via BigQuery external tables                                 | https://github.com/cal-itp/data-infra/tree/main/jobs/gtfs-rt-parser-v2                           | https://github.com/cal-itp/data-infra/tree/main/jobs                          | https://ghcr.io/cal-itp/data-infra/gtfs-rt-parser-v2       | Docker Image   |
 | gtfs-schedule-validator | Wrapper for the MobilityData GTFS Schedule validator (so we can choose to use the correct version for the age of a given data import) | https://github.com/cal-itp/data-infra/tree/main/jobs/gtfs-schedule-validator                     | https://github.com/cal-itp/data-infra/tree/main/jobs                          | https://ghcr.io/cal-itp/data-infra/gtfs-schedule-validator | Docker Image   |
 | jupyter-singleuser      | Shared, consistent tooling for individual local Jupyter notebook users and JupyterHub                                                 | https://github.com/cal-itp/data-infra/tree/main/images/jupyter-singleuser                        | https://github.com/cal-itp/data-infra/tree/main/images/jupyter-singleuser     | https://ghcr.io/cal-itp/data-infra/jupyter-singleuser      | Docker Image   |

docs/architecture/images_and_packages.md

@@ -7,7 +7,7 @@ Each subfolder here corresponds to a Docker image that utilizes a standalone scr
 A person with Docker set up locally can build a new version of each image at any time after making changes. From the relevant subfolder, run
 
 ```bash
-docker build -t ghcr.io/cal-itp/data-infra/[gtfs-aggregator-parser/gtfs-rt-parser-v2/gtfs-schedule-validator/etc.]:[NEW VERSION TAG] .
+docker build -t ghcr.io/cal-itp/data-infra/gtfs-schedule-validator:[NEW VERSION TAG] .
 ```
 
 That image can be used alongside [a local Airflow instance](../airflow/README.md) to test the changed job locally prior to merging.
@@ -17,8 +17,8 @@ That image can be used alongside [a local Airflow instance](../airflow/README.md
 When changes are finalized, a new version number should be specified in the given subfolder's `pyproject.toml` file. When changes to this directory are merged into `main`, a GitHub Action called `build-[JOB NAME]` automatically publishes an updated version of the image. A contributor with proper GHCR permissions can also manually deploy a new version of the image via the CLI:
 
 ```bash
-docker build -t ghcr.io/cal-itp/data-infra/[gtfs-aggregator-parser/gtfs-rt-parser-v2/gtfs-schedule-validator/etc.]:[NEW VERSION TAG] .
-docker push ghcr.io/cal-itp/data-infra/[gtfs-aggregator-parser/gtfs-rt-parser-v2/gtfs-schedule-validator/etc.]:[NEW VERSION TAG]
+docker build -t ghcr.io/cal-itp/data-infra/gtfs-schedule-validator:[NEW VERSION TAG] .
+docker push ghcr.io/cal-itp/data-infra/gtfs-schedule-validator:[NEW VERSION TAG]
 ```
 
-After deploying, no additional steps should be necessary. All internal code referencing the `gtfs-aggregator-scraper`, `gtfs-rt-parser-v2`, and `gtfs-schedule-validator` jobs utilize [the Airflow image_tag macro](../airflow/dags/macros.py) to automatically fetch the latest version during DAG runs.
+After deploying, no additional steps should be necessary. All internal code referencing the `gtfs-schedule-validator` jobs utilize [the Airflow image_tag macro](../airflow/dags/macros.py) to automatically fetch the latest version during DAG runs.