Add test for example and template to be valid frictionless datapackage

[Ludee]

Summary of the discussion

Use frictionless-py validate function in tests.

Type of change (CHANGELOG.md)

Added

• Tests for example and template to be valid frictionless datapackage (#305)

Workflow checklist

Automation

Closes #290 / Part of #296

PR-Assignee

• 🐙 Follow the workflow in CONTRIBUTING.md
• 📝 Update the CHANGELOG.md
• 📙 Update the documentation
• 🐙 Assign a reviewer to the PR

Reviewer

• 🐙 Follow the Reviewer Guidelines
• 🐙 Provided feedback and show sufficient appreciation for the work done

[jh-RLI]

I suggest tp focus on this PR before continuing work on the other "oem content" related PR´s

Most tests are failing as you used "type": "text", instead of "type": "string",

Please also put the option of "null" if a property is not required:

          "type": [
            "string",
            "null"
          ],

[jh-RLI]

integer is okay, most times there is something wit a range of bits. There might be infinit rows in the dataset.

I think this is not relevant for this example so just a comment.

[jh-RLI]

I will have to test this as it might change how this is handled e.g. in the OEP.

There is a diff. between json.load and .loads. we should keep ".loads" and also the "rb" mode.

But as this is scoped to this version it iwll not break things ... at least for now ;)

[jh-RLI]

Maybe you handle this here already

Package(descriptor, basepath=str(BASE_PATH))

[jh-RLI]

In general we can just merge this. But we need to check the changes to the module import functionality for example and template in all cases where we integrated oemetadata and or omi.