fix(anthropic): include cached tokens in usage count logs

[evalstate]

cache_creation_input_tokens and cache_read_input_tokens were not being
added to the usage total recorded in goose.log. This fix includes
those categories in the calculation of "input tokens" as per the API guide.

refs: https://docs.anthropic.com/en/docs/build-with-claude/prompt-caching#tracking-cache-performance

[evalstate]

Earlier failures were due to:

1. Formatting issue
2. Clippy failure

Branch updated to latest and

• cargo clean
• cargo clippy
• cargo build
• cargo test

run clean.

The development build has been re-tested, the highlighted entry is from ./target/debug/goose and usage verified with the anthropic console.

The warning:

[Lint Electron Desktop App: ui/desktop/src/App.tsx#L77](https://github.com/block/goose/pull/947/files#annotation_31733017641)
Unexpected any. Specify a different type

is not introduced by this change.

[angiejones]

thank you @evalstate!

@salman1993 good with merging this one?

[lily-de]

Hi @evalstate,

Thank you for your contribution! Before we can proceed with merging your pull request, it needs to be updated with the latest changes from the main branch to ensure compatibility and ease of integration. Here are the steps you can follow to update your branch:

1. Ensure Your Local Main Branch is Up to Date:
   First, make sure you have the latest changes from the main repository:

   git checkout main
   git pull upstream main

   Replace upstream with the remote name of the main repository if you've used a different one.

2. Checkout Your PR Branch:
   Switch back to your branch associated with the pull request:

   git checkout [your-branch-name]

3. Merge or Rebase Main into Your Branch:
   You can either merge the main branch into your PR branch to maintain the history, or rebase for a cleaner commit history. Here’s how you can do both:

   • Merge:

     git merge main

     This command will bring your branch up to date with the main branch while preserving the history of changes.

   • Rebase:

     git rebase main

     Rebasing will linearize your commit history based on the main branch. If you encounter conflicts during rebase, you’ll need to resolve them and then continue the rebase with git rebase --continue.

4. Push the Updated Branch:
   After merging or rebasing, push your branch to update the pull request:

   git push origin [your-branch-name] --force

   Use the --force flag if you've performed a rebase or otherwise rewritten the history.

Once you've updated your branch, please let me know by commenting on the pull request, and I'll take another look.

Thank you!