chore: updates msi-adapter image

[nilekhc]

Reason for Change:

Updates MSI Adapter to address vulnerability fixes.

Requirements

• squashed commits
• included documentation
• added unit tests and e2e tests (if applicable).

Issue Fixed:

Does this change contain code from or inspired by another project?

• Yes
• No

If "Yes," did you notify that project's maintainers and provide attribution?

Special Notes for Reviewers:

[nilekhc]

/azp run pr-e2e-azure

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (master@e36fd57). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1103   +/-   ##
=========================================
  Coverage          ?   56.34%           
=========================================
  Files             ?       10           
  Lines             ?     1072           
  Branches          ?        0           
=========================================
  Hits              ?      604           
  Misses            ?      443           
  Partials          ?       25           

[aramase]

I don't see these changes being validated as part of the CI. Could we set enableMonitoring=true as part of e2e_arc_test and check these pods are up and running as a confirmation in the CI?

[nilekhc]

I don't see these changes being validated as part of the CI. Could we set enableMonitoring=true as part of e2e_arc_test and check these pods are up and running as a confirmation in the CI?

@aramase I added a check and it's passing in test run -
https://dev.azure.com/AzureContainerUpstream/Secrets%20Store%20CSI%20Driver%20Provider%20Azure/_build/results?buildId=84644&view=logs&j=635f5725-01ef-54e0-2420-bc6282236cc8&t=72aaed19-673d-56a4-af6e-e330415d20fd&l=66

[aramase]

/azp run pr-e2e-azure

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).