A few more clippy fixes

[john-h-kastner-aws]

Description of changes

Issue #, if available

Checklist for requesting a review

The change in this PR is (choose one, and delete the other options):

• A breaking change requiring a major version bump to cedar-policy (e.g., changes to the signature of an existing API).
• A backwards-compatible change requiring a minor version bump to cedar-policy (e.g., addition of a new API).
• A bug fix or other functionality change requiring a patch to cedar-policy.
• A change "invisible" to users (e.g., documentation, changes to "internal" crates like cedar-policy-core, cedar-validator, etc.)
• A change (breaking or otherwise) that only impacts unreleased or experimental code.

I confirm that this PR (choose one, and delete the other options):

• Updates the "Unreleased" section of the CHANGELOG with a description of my change (required for major/minor version bumps).
• Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

• Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.
• Requires updates, and I have made / will make these updates myself. (Please include in your description a timeline or link to the relevant PR in cedar-spec, and how you have tested that your updates are correct.)
• Requires updates, but I do not plan to make them in the near future. (Make sure that your changes are hidden behind a feature flag to mark them as experimental.)
• I'm not sure how my change impacts cedar-spec. (Post your PR anyways, and we'll discuss in the comments.)

I confirm that docs.cedarpolicy.com (choose one, and delete the other options):

• Does not require updates because my change does not impact the Cedar language specification.
• Requires updates, and I have made / will make these updates myself. (Please include in your description a timeline or link to the relevant PR in cedar-docs. PRs should be targeted at a staging-X.Y branch, not main.)
• I'm not sure how my change impacts the documentation. (Post your PR anyways, and we'll discuss in the comments.)

[github-actions]

Coverage Report

Head Commit: 36be06d379e3ad8b6fb404161da56d24e1366915

Base Commit: 289e060d86d27507a7b09f6f931877d517785199

Download the full coverage report.

Coverage of Added or Modified Lines of Rust Code

Required coverage: 80.00%

Actual coverage: 77.78%

Status: FAILED ❌

Details

File	Status	Covered	Coverage	Missed Lines
cedar-policy-cli/src/lib.rs	🔴	2/3	66.67%	959
cedar-policy-core/src/ast/policy.rs	🟡	3/4	75.00%	1160
cedar-policy/src/api.rs	🟢	2/2	100.00%

Coverage of All Lines of Rust Code

Required coverage: 80.00%

Actual coverage: 80.77%

Status: PASSED ✅

Details

Package	Status	Covered	Coverage	Base Coverage
cedar-policy	🔴	3059/4392	69.65%	69.65%
cedar-policy-cli	🔴	538/927	58.04%	58.14%
cedar-policy-core	🟢	11326/13775	82.22%	82.23%
cedar-policy-formatter	🟢	914/1043	87.63%	87.63%
cedar-policy-validator	🟢	8242/9647	85.44%	85.44%
cedar-wasm	🔴	0/29	0.00%	0.00%

[adpaco-aws]

This one surprised me. What lint is this?

[john-h-kastner-aws]

This one i think https://rust-lang.github.io/rust-clippy/master/index.html#or_fun_call