fix!: Fix field selection and bugs in ProjectsV2 GET endpoints

[stephenotalora]

BREAKING CHANGE: UpdateProjectItemOptions.Field is now []*ProjectV2FieldUpdate.

Discovered these issues while integrating the related project item APIs exposed in V77.

Fixes bugs in the implementation of support for field selection and updates in the following project item endpoints:

• Properly handles URL parameters for field selection in GetOrganizationProjectItem and GetUserProjectItem.
• Corrects field update struct and request payload formatting in UpdateOrganizationProjectItem and UpdateUserProjectItem.

Adds or updates tests to verify correct handling of these cases.

Covers:
https://docs.github.com/en/rest/projects/items?apiVersion=2022-11-28

Related REST API docs:

• https://docs.github.com/en/rest/projects/items#get-a-project-item
• https://docs.github.com/en/rest/projects/items#update-project-item-for-organization
• https://docs.github.com/en/rest/projects/items#get-a-project-item-for-a-user
• https://docs.github.com/en/rest/projects/items#update-project-item-for-a-user

Complements: #3793

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.33%. Comparing base (1b4b8cc) to head (9f0e22e).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #3809 +/- ##
=======================================
Coverage 92.32% 92.33% =======================================
Files 194 194 Lines 13984 13990 +6 =======================================
+ Hits 12911 12917 +6 
Misses 884 884 Partials 189 189 

☔ View full report in Codecov by Sentry.
📢 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.

[gmlewis]

Thank you, @stephenotalora!
Please add testBadOptions to all your new unit tests to improve the code coverage.

[stephenotalora]

Thank you, @stephenotalora! Please add testBadOptions to all your new unit tests to improve the code coverage.

Good catch, @gmlewis 🙇🏼 fixed! I was deep in the bug fixes and glossed over that. 👍

[gmlewis]

Thank you, @stephenotalora!
LGTM.
Awaiting second LGTM+Approval from any other contributor to this repo before merging.

cc: @stevehipwell - @alexandear - @zyfy29

[alexandear]

Why not?

Suggested change

	typeProjectV2FieldUpdatestruct {
	typeUpdateProjectV2Fieldstruct {

[stephenotalora]

This has been fixed as part of 3bbb927

[stephenotalora]

@alexandear@gmlewis I need to make an adjustment to the API payload for fields before moving this forward. We identified a discrepancy between the documented schema and the payload currently returned by the server. I’m converting this PR back to draft while I align the affected structs with the updated documentation. I should be able to reopen the PR tomorrow and will share the new commits once they're ready. I'll also address recent feedback, Thanks for your patience!

[stephenotalora]

@alexandear@gmlewis I need to make an adjustment to the API payload for fields before moving this forward. We identified a discrepancy between the documented schema and the payload currently returned by the server. I’m converting this PR back to draft while I align the affected structs with the updated documentation. I should be able to reopen the PR tomorrow and will share the new commits once they're ready. I'll also address recent feedback, Thanks for your patience!

@gmlewis I’ve resolved the discrepancy noted earlier in commit 3bbb927 and verified the changes against production data S2S using google/go-github pointing to my branch (via go.mod). The issue was caused by slightly inaccurate OpenAPI definitions on our end, which I’ve now corrected to reflect the expected payload shape. The primary change introduced in this commit (3bbb927) is the addition of a dedicated struct for text-based fields: ProjectV2TextContent which contains (raw + html) fields to accurately represent the server response for the corresponding Projects APIs.

For concrete examples, click to expand

API	Github Docs	Server Response
items
fields

Without the fix in 3bbb927, the request resulted in unmarshal errors due to mismatched object shapes.

[gmlewis]

OK, so this is now ready for merging, correct, @stephenotalora?
@alexandear - are you OK for this PR to be merged?

[stephenotalora]

OK, so this is now ready for merging, correct, @stephenotalora?

Yes, correct, ready to go, tested quite extensively S2S today 👍🏼

[alexandear]

I'm OK.

[gmlewis]

Thank you, @stephenotalora and @alexandear!
Merging.

[stephenotalora]

Thank you, @stephenotalora and @alexandear! Merging.

Thanks so much for getting this merged, @gmlewis! 🙏🏼 Do you happen to know when the next release might be planned? I’d love to start using the latest changes downstream. Thanks again 🙇🏼

[gmlewis]

Thanks so much for getting this merged, @gmlewis! 🙏🏼 Do you happen to know when the next release might be planned? I’d love to start using the latest changes downstream. Thanks again 🙇🏼

We just made two quick releases in a row based on requests, but we could probably do another release after #3814 gets merged.

[gmlewis]

This is now available here:
https://github.com/google/go-github/releases/tag/v79.0.0