Update morrow to 1.1.0

[Prodesire]

Summary

Update morrow from 0.7.0 to 1.1.0, built with Mojo 1.1.0. As other recipes do, mojo_version is set in the recipe context, and the build, host, and run requirements all pin mojo-compiler =1.1.0. Projects on Mojo 1.0 keep resolving the existing 0.7.0 build, which requires <1.1.0.

1.1.0 adds 81 locales, hashable date-time values, timezone abbreviations, and pure-Mojo tzdata timezones. ICU stays a runtime fallback (icu >=69) for zones without a system zone file.

Validation

• Upstream CI tests and precompiles the source with Mojo 1.0.0 and 1.1.0 on Linux x86-64, Linux ARM64, and macOS ARM64.
• The release workflow extracts each release archive and runs test.mojo outside the source checkout.

Checklist

• Compiler compatibility is set in the recipe context.
• Source is pinned to the release commit.
• The build number resets to 0 for the new version.

[alisterburt]

hey @Prodesire, looks like the recipe is failing to parse: mojo_version is coming through empty so mojo-compiler ==${{ mojo_version }} ends up as mojo-compiler ==, which rattler-build can't parse (unable to parse version spec: ==)
https://github.com/modular/modular-community/actions/runs/36659718417/job/109711564326?pr=379

should be an easy fix, defining mojo_version in the context: block (like the other recipes do) rather than in a separate variants.yaml should sort it! To make it easier to know what's ready for review I'm closing PRs with failing builds, please reopen when you've had a chance to update this 🙂