(BSR) refactor(qpi): remove useless tasks in import dag

[vbusson-pass]

DE PR

Describe your changes

Please include a summary of the changes:

• This PR [adds/removes/fixes/replaces] the [feature/bug/etc].
• Tag a reviewer if necessacy @github/username

Jira ticket number and/or notion link

JIRA-ticket_number

Type of change

• Fix (non-breaking change which corrects expected behavior)
• New fields (non-breaking change)
• New table (non-breaking change)
• Concept change (potentially breaking change which modifies fields according to new or evolving business concepts)
• Table deletion (potentially breaking change which adds functionality/ table)

Checklist before requesting a review

• I have performed a self-review of my code

• My code passes CI/CD tests

• I updated README.md

• I have updated the dag

• If my changes concern incremental table, I have altered their schema to accomodate with field's creation/deletion

• I have made corresponding changes to the tables documentation

• I have made corresponding changes to the fields glossary

• I will create a review on slack and ensure to specify the duration of the review task: short (<10min), medium (<30min), long (>30min)

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help
• ⏰ no, but I created a ticket

PR title format (except for MEP)

There is a linter on the PR title format. Please respect the following format:

(ticket) type(topic): comment

• ticket surrounded by parenthesis, with optionnaly a hyphen followed by one or more digits (e.g., -1234). The first part must be one of the following strings:

  • DA
  • DE
  • AE
  • DS
  • HF
  • BSR
  • PC

• type :
  The second part to specify the type of change one of the following :

  • build
  • lint
  • ci
  • docs
  • feat
  • fix
  • perf
  • refactor
  • test
  • core
  • dbt

• topic within parenthesis: 1 word e.g., (dag)

• comment: tell us your life

examples:

• ✅ (DE-124) refactor(firebase): update source field
• ❌ (DE-124) refactor (firebase): update source field (space between type and topic)
• ❌ (DE-124) airflow(firebase): update source fiedd in DAG (wrong type)
• ❌ (DE-124) (DE-124) refactor(firebase refacto): update source field (topic in two words)
• ✅ (BSR) docs(github): add PR title valid format in template

[lmontier-pass]

ok pour moi. Juste un petit renommage et minirefacto de la fonction ça serait plus clair. (même si je sais que ce n'est pas toi qui vient de mettre ce code)

• verify_folder => check_folder_is_not_empty
• blob_list = [ file for file in bucket.list_blobs(prefix=name)]

Et enfin, ça pourrait être pas mal de créer des constantes pour les task_id qui sont liés à des branch_operator

genre
END_TASK_ID = "end"
IMPORT_ANSWERS_TO_BQ_TASK_ID=import_historical_answers_to_bigquery