updates for JSON v1

[lazarusA]

this PR includes all the necessary updates for JSON V1.

For now, I’ve added my own AWS branch, which also needed some updates to make this work.

All tests passed for me locally, let's see how CI behaves.

Merging and patching here should be done after JuliaCloud/AWS.jl#741 is also merged and patch released.

[mkitti]

How long do you think we need the AWS.jl fork?

[lazarusA]

How long do you think we need the AWS.jl fork?

until JuliaCloud/AWS.jl#741 is merged and patch released 😄

[lazarusA]

should we add AWS to the compats main project.toml ? @meggart

[mkitti]

Would AWS.jl make sense as an optional dependency via a package extension?

[coveralls]

Pull Request Test Coverage Report for Build 19541885018

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 5 of 6 (83.33%) changed or added relevant lines in 4 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.01%) to 89.309%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/Storage/gcstore.jl	0	1	0.0%

Totals
Change from base Build 19048552340:	0.01%
Covered Lines:	969
Relevant Lines:	1085

---

💛 - Coveralls

[lazarusA]

Would AWS.jl make sense as an optional dependency via a package extension?

yes, next we will put all AWS related stuff into an extension.

[mkitti]

If this works, I am good to merge and release this.

[meggart]

Yes, I would also merge the JSON v1 updates for now and then we can move AWS-related things to an extension in a follow-up PR.