feat: add fail_project_under and fail_any_model_under options

[WobblyRobbly]

This pull request is for Issue #55

Decisions

• fail_project_under and fail_any_model_under can be specified in the pyproject.toml or via command line
• to avoid making this a breaking change a default value of 0.0 for fail_project_under and fail_any_model_under is set
• the exit point for failing is in cli.py and that required the Evaluation instance to be returned from lint_dbt_project

Please let me know your thoughts of potential changes

Closes #55

[WobblyRobbly]

@jochemvandooren as we've added a Breaking Change i.e. will fail if the default model score isn't met (5.0) this should bump the version to 1.0.0 based on ?

## [1.0.0] - 2024-06-19

- Add `project_fail_under` configuration 
- Add `fail_any_model_under` configuration
- **breaking:** - default values of `5.0` for `project_fail_under` and `fail_any_model_under` will cause command to exit return code 1

[matthieucan]

@jochemvandooren as we've added a Breaking Change i.e. will fail if the default model score isn't met (5.0) this should bump the version to 1.0.0 based on ?

## [1.0.0] - 2024-06-19

- Add `project_fail_under` configuration 
- Add `fail_any_model_under` configuration
- **breaking:** - default values of `5.0` for `project_fail_under` and `fail_any_model_under` will cause command to exit return code 1

We're following semantic versioning, meaning if the major version is 0, a breaking change will bump the minor version. However no need for this to happen in the changelog file for this PR, this is done when releasing :)

[matthieucan]

@WobblyRobbly Thank you so much for your contribution! First external PR that we merged for this project 🚀 🥇 Looking forward to more of the same!

[WobblyRobbly]

Thanks for all your help on this one !!