feat: Add simple CRUD endpoints for GitHub Copilot Spaces

[Ackberry]

Adds support for the core organization Copilot Spaces endpoints:

• List organization Copilot Spaces
• Get an organization Copilot Space
• Create an organization Copilot Space
• Update an organization Copilot Space
• Delete an organization Copilot Space

Solves #4238 partially.

[gmlewis]

@Ackberry - please run step 4 of CONTRIBUTING.md and push the changes to this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.53%. Comparing base (9549a7a) to head (2c582e7).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4379   +/-   ##
=======================================
  Coverage   97.52%   97.53%           
=======================================
  Files         193      193           
  Lines       19668    19737   +69     
=======================================
+ Hits        19182    19251   +69     
  Misses        268      268           
  Partials      218      218           

☔ 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.

[Ackberry]

fixed lint errors.

[gmlewis]

Thank you, @Ackberry!
Now please work through the official GitHub v3 API documentation and find the "required" fields for each struct and make them values instead of pointers, and remove the omitempty from the required fields. If fields are shared by multiple endpoints and sometimes they are optional and sometimes they are required, then we do actually want to leave them as pointers with omitempty as they are not ALWAYS required. However, if they are ALWAYS required, then please use values and no omitempty.

Here's an example of what I'm talking about:

[Ackberry]

okay, instead of all being optional at the moment, I would set the required ones intact as per github docs. on it!

[gmlewis]

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

cc: @stevehipwell - @alexandear - @Not-Dhananjay-Mishra

[gmlewis]

Whups, I didn't wait for the linter again.
Please follow step 4 of CONTRIBUTING.md and push the changes to this PR.

[Ackberry]

huh, interesting. I did run the lint and other scripts in place.

[Ackberry]

the workflow returned a 502 error, perhaps you can rerun the workflow? might be an issue on github api side

[gmlewis]

the workflow returned a 502 error, perhaps you can rerun the workflow? might be an issue on github api side

Sorry about that... my bad! Reran and all is well.

[Ackberry]

sounds good! will get to the next PR now. Will share my plan on the issue before proceeding

[Ackberry]

I split the create and update endpoint structs, and also created a new metadata struct. For metadata tests, I only used the name and text because all other metadata fields use the same JSON struct-tag marshal/unmarshal path. That said, I can add a focused issue/PR metadata case if you’d prefer explicit coverage for those resource items.

[alexandear]

Looks like we should change *string to *int:

              copilot_chat_attachment_id:
                type: integer
                format: int64
                nullable: true
                description: The unique identifier of the chat attachment for uploaded
                  files or media content.

The same for other places in the PR.