Migrate module support for Projects (classic) to Projects

Feature Idea Summary

GitHub released a new version of Projects in July 2022 which is built on top of Issues.

When that happened, they deprecated the old version of Projects by renaming them "Projects (classic)", and turning off the ability for users to create new Classic Projects. You can still manipulate existing Classic Projects, but any new Projects created are the new version (which are simply named "Projects".

Feature Idea Additional Details

From the "Projects (classic)" documentation:

These endpoints only interact with projects (classic). To manage Projects, use the GraphQL API. For more information, see "Using the API to manage projects."

To create a new classic project, the organization, user, or repository must already have at least one classic project.

This work will require renaming the existing API's to follow a pattern like Get-GitHubProject to Get-GitHubProjectClassic (as well as the file names) so that the current API names can be repurposed for the new API set.

Requested Assignment

This work is up-for-grabs.

Operating System

OsName               : Microsoft Windows 10 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.19041.2364
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.2364
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Module Version

Running: 0.16.1
Installed:

microsoft / PowerShellForGitHub