build(deps): Bump actions/upload-artifact from 4.6.0 to 4.6.1

[dependabot]

Bumps actions/upload-artifact from 4.6.0 to 4.6.1.

Release notes

Sourced from actions/upload-artifact's releases.

v4.6.1

What's Changed

• Update to use artifact 2.2.2 package by @​yacaovsnc in actions/upload-artifact#673

Full Changelog: actions/upload-artifact@v4...v4.6.1

Commits

• 4cec3d8 Merge pull request #673 from actions/yacaovsnc/artifact_2.2.2
• e9fad96 license cache update for artifact
• b26fd06 Update to use artifact 2.2.2 package
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Test Results

 17 files  ± 0  103 suites  ±0   25m 22s ⏱️ +27s
370 tests +11  352 ✅ +11  18 💤 +2  0 ❌  - 2 
467 runs  ± 0  447 ✅ ± 0  20 💤 +2  0 ❌  - 2 

Results for commit c3e5902. ± Comparison against base commit 5085a5a.

This pull request removes 1 and adds 12 tests. Note that renamed tests count towards both.

"before each" hook for "should fail when trying to update fees of non fungible token with no fee schedule key" ‑ TokenManagmentContract Test Suite Update fees "before each" hook for "should fail when trying to update fees of non fungible token with no fee schedule key"

should fail for updateFungibleTokenCustomFees when token is not associated to fee collector ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail for updateFungibleTokenCustomFees when token is not associated to fee collector
should fail for updateNonFungibleTokenCustomFees when token is not associated to fee collector ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail for updateNonFungibleTokenCustomFees when token is not associated to fee collector
should fail when fee has negative values for non fungible token ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when fee has negative values for non fungible token
should fail when fee has negative values ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when fee has negative values
should fail when fractional fee has denominator zero ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when fractional fee has denominator zero
should fail when the provided fee collector is invalid for NFT ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when the provided fee collector is invalid for NFT
should fail when the provided fee collector is invalid ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when the provided fee collector is invalid
should fail when the provided token id is invalid for NFT ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when the provided token id is invalid for NFT
should fail when the provided token id is invalid ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when the provided token id is invalid
should fail when trying to update fees of non fungible token with no fee schedule key ‑ TokenManagmentContract Test Suite Update fees Update fees negative cases should fail when trying to update fees of non fungible token with no fee schedule key
…