✨ Add Eurostat source and Prefect tasks

[adrian-wojcik]

Summary

Adding Eurostat connector

Importance

To use Eurostat in Prefect 2.0

Checklist

This PR:

• follows the guidelines laid out in CONTRIBUTING.md
• links relevant issue(s)
• adds/updates tests (if appropriate)
• adds/updates docstrings (if appropriate)
• adds an entry in CHANGELOG.md

[trymzet]

Added my comments

[trymzet]

Added my feedback. It might be easier to create one issue to address the changes for which I haven't added suggestions (except unit tests as these should be fixed before merging).

[trymzet]

1. Looks like the unit tests still don't mock the API calls.
2. It seems docs are also not added. See https://viadot.docs.dyvenia.com/developer_guide/creating_a_source/#adding-docs and https://viadot.docs.dyvenia.com/developer_guide/creating_a_prefect_flow/#adding-docs
3. There's one open conversation left from before

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
6616985	Triggered	Generic Password	c3589a1	tests/unit/test_business_core.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[trymzet]

@Rafalz13 the other "unit" tests are also not unit tests; they try to connect to the actual API. So the mocking in general is incorrect and needs fixing (once you fix it you might as well re-add the to_df() test since it used the same mocking logic as other tests?)

[Rafalz13]

@zawadzki Tests don't connect to the source after changes. Test coverage is 80%.