chore(deps): bump dependency versions

[joshsmithxrm]

Summary

• Azure.Identity 1.13.* → 1.17.*
• Microsoft.Extensions.DependencyInjection 10.0.1 → 10.0.2
• Microsoft.Extensions.DependencyInjection.Abstractions 10.0.1 → 10.0.2
• Microsoft.Extensions.Configuration 10.0.1 → 10.0.2
• Microsoft.Extensions.Configuration.Binder 10.0.1 → 10.0.2
• Microsoft.Extensions.Configuration.Json 10.0.1 → 10.0.2
• actions/setup-node v4 → v6
• actions/upload-artifact v4 → v6

Consolidates dependabot PRs #494, #495, #496, #498, #499, #505, #506.

Test plan

• CI passes

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @joshsmithxrm, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on maintaining the project's health and security by updating several core dependencies to their latest stable versions. The updates encompass a significant bump for Azure authentication libraries and minor version increments for various Microsoft Extension packages, which collectively enhance stability, performance, and address known vulnerabilities. This consolidation streamlines multiple dependency updates into a single, manageable change.

Highlights

• Azure.Identity Update: The Azure.Identity package has been updated from version 1.13.* to 1.17.*, bringing the latest authentication features and security enhancements for Azure services.
• Microsoft.Extensions Package Updates: Multiple Microsoft.Extensions.* packages, including DependencyInjection, Logging.Abstractions, Options, and Configuration related packages, have been updated from version 10.0.1 to 10.0.2 across various projects, ensuring minor bug fixes and improvements.
• Security Patch for Cryptography Package: The System.Security.Cryptography.Pkcs package has been explicitly updated from 10.0.1 to 10.0.2 in PPDS.Dataverse.csproj to override a vulnerable transitive dependency.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/tui-e2e.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates several dependencies across the solution, including Azure.Identity and various Microsoft.Extensions.* packages. The changes are straightforward version bumps. My review includes a suggestion to pin the Azure.Identity package to a specific version to ensure reproducible builds, which is a common best practice for dependency management. The other dependency updates look good.

[gemini-code-assist]

To improve build reproducibility and prevent unexpected changes, it's a best practice to pin package versions to a specific version instead of using wildcards. This ensures that everyone on the team and in CI/CD pipelines uses the exact same version of the dependency. Please consider pinning Azure.Identity to a specific version, such as 1.17.0.

    <PackageReference Include="Azure.Identity" Version="1.17.0" />