⚙️ Build testing client facing Dewrangle prd

[XuTheBunny]

Summary:
I’m consolidating our Dewrangle-related logic and tests into d3b-api-client-cli, with the goal of creating a safe, controlled place to test against Dewrangle (PRD) without impacting other workflows.

Stage 1 – In Progress (d3b-api-client-cli consolidation)

Work completed / ongoing:

• Cleaning up here by removing obsolete Dewrangle queries and mutations.
• Moving over the necessary Dewrangle queries, mutations, and CLI command scripts from kf-etl-dataservice-dewrangle.
• Ensuring all existing unit tests (especially Dewrangle-related) are running successfully in the updated repo.
• Migrating Dewrangle integration tests from kf-etl-dataservice-dewrangle
• Refactoring conftest.py and adjusting test data so integration tests can run without standing up a local Dataservice Docker stack.
• Setting up Dewrangle token configuration for local testing and adding the appropriate GitHub secret for CI.
• Update existing unit and integration tests in here
• Breaking changes into multiple focused PRs for easier review.
• Writing a README / developer guide to help the team better navigate and use this repo.

Stage 2 – Planned

• Once tests are stable and passing in d3b-api-client-cli, remove duplicated Dewrangle logic/tests from kf-etl-dataservice-dewrangle (merge into develop).
• Use the develop branch as a testing ground for:
  • Our end-to-end testing strategy (which requires standing up Dataservice via Docker).
  • Defining how kf-etl-dataservice-dewrangle should communicate with d3b-api-client-cli.

Pull request planning

• Step 1: (PR1) Create a develop branch to serve as a temporary consolidation branch for all changes related to the test migration work.
• Step 2: (PR2) Migrate Dewrangle-related files and integration tests, replacing existing implementations.
  • Important: In this PR I will:
    • Remove db and faker files/functions from d3b-api-client-cli.
    • Remove db and faker unit and integration tests in d3b-api-client-cli
      • Unit tests: db, dewrangle, faker
      • Integration tests: db
• Step 3: (PR3) Rewrite unit tests for dewrangle.
  • Important: Here we need to make a decision on if we still want to add back db and faker related code/tests
    • My suggestion: Don't add back the code and tests for  db and faker , this repo has been repurposed for testing against Dewrangle, we want to keep it focused on that.