[breaking][deps] bump linodego to v2

[AshleyDumaine]

General:

• Have you removed all sensitive information, including but not limited to access keys and passwords?
• Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?

Pull Request Guidelines:

1. Does your submission pass tests?
2. Have you added tests?
3. Are you addressing a single feature in this PR?
4. Are your commits atomic, addressing one change per commit?
5. Are you following the conventions of the language?
6. Have you saved your large formatting changes for a different PR, so we can focus on your work?
7. Have you explained your rationale for why this feature is needed?
8. Have you linked your PR to an open issue

linodego v1 is not receiving backports for features going into the new v2 (which has been out for a month).
See https://github.com/linode/linodego/blob/main/docs/linode_v2_migration_guide.md

[codecov]

Codecov Report

❌ Patch coverage is 91.48936% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.68%. Comparing base (68eacfd) to head (713f128).

Files with missing lines	Patch %	Lines
cloud/linode/client/client.go	60.00%	1 Missing and 1 partial ⚠️
cloud/linode/loadbalancers.go	93.33%	1 Missing ⚠️
cloud/linode/services/firewalls.go	95.45%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #585      +/-   ##
==========================================
+ Coverage   73.65%   73.68%   +0.02%     
==========================================
  Files          19       19              
  Lines        3029     3036       +7     
==========================================
+ Hits         2231     2237       +6     
  Misses        538      538              
- Partials      260      261       +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.