Fix Code Scanning Alert tool field

[ganeshkumarsv]

The tool field on the API response of listing code scanning alerts is a struct instead of a string. This PR fixes the alert tool field to a struct.
Github API: https://docs.github.com/en/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository

Deprecation notice from Github: The tool_name field is deprecated and will, in future, not be included in the response for this endpoint. The example response reflects this change. The tool name can now be found inside the tool field.
https://docs.github.com/en/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[ganeshkumarsv]

@googlebot I signed it!

[gmlewis]

Thank you, @ganeshkumarsv !

[codecov]

Codecov Report

Merging #1904 (ce450a9) into master (75644ea) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1904   +/-   ##
=======================================
  Coverage   97.65%   97.65%           
=======================================
  Files         105      105           
  Lines        6786     6786           
=======================================
  Hits         6627     6627           
  Misses         86       86           
  Partials       73       73           

Impacted Files	Coverage Δ
github/code-scanning.go	100.00% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 75644ea...ce450a9. Read the comment docs.

[stephengroat]

these might help

[gmlewis]

Thank you, @ganeshkumarsv !
LGTM.

Awaiting second LGTM before merging.

[gmlewis]

I apologize for the PR name changes. I see now that this is a "fix" and not an addition... and is therefore a breaking API change.

[gmlewis]

Friendly ping @wesleimp

[ganeshkumarsv]

@gmlewis @wesleimp
gentle bump

[ganeshkumarsv]

@gmlewis @wesleimp
Can we get one more review for the PR please? We are not able to use go-github because of the issue in Alert tool field.

[gmlewis]

@gmlewis @wesleimp
Can we get one more review for the PR please? We are not able to use go-github because of the issue in Alert tool field.

Please feel free to have any contributor to this repo provide a code review and approval, and we will get this merged. Thanks.

[Parker77]

LGTM.