Update project for Fusion compatibility

[matthewshaver]

This PR updates the Jaffle Shop project to run without deprecation warnings or errors on both Latest and Fusion Latest in the dbt platform:

• Refactors project based on new syntax and behavior changes (used autofix tool)
• Updates packages to Fusion-compatible versions (also with autofix tool)
• As the YAML spec for Semantic Layer is different for Fusion, we have removed any SL metrics, queries, and files from the project. Once the YAML spec has been ported to Latest as well, we will re-introduce in the new format

Ran project locally in Fusion with Snowflake and got a successful build with 0 warnings or errors

[b-per]

@matthewshaver

• should we add a minimum dbt version that people can use this project with now, then? https://docs.getdbt.com/reference/project-configs/require-dbt-version
  • i don't think that we support arguments: in versions before 1.10 but we'd need to check
• as a follow-up from above, should we have a long-living branch that would work for all Core versions (e.g. more or less what the code is today) but not on Fusion?
• and should we mention the above distinctions in the README somewhere?

[matthewshaver]

@b-per Yes, all good points. I need to do a little more testing with this version in the platform and ensure I can switfly swtich between extended/compatible/latest/latest fusion with little to no friction. Once I've done that:

• I'll update the README
• Check for how far back some features have been backported

As for a long-living branch for older versions, I'll defer to you and your team. From the docs side, we're taking the approach to only document and use examples for currently supported versions, which would exclude those older requriements. If you want to keep this Jaffle Shop functional for unsupported versions that still appear in the selection menu, I'm happy to help