Improvements to GitHub Team API's

[HowardWolosky]

Description

#257 did a fantastic job closing the gap on missing functionality in the module related to GitHub Teams.
This PR just adds onto that work by providing options that will reduce the need for additional queries during common operations.

• Get-GitHubTeam: Breaking Change Looking up a team by its ID has been deprecated per GitHub documentation. Removed that functionality and added the ability to look up by slug instead. This also means that you can now pipe in a team and get back the specific result without needing to filter through all org results.

• Get-GitHubTeamMember: Updated to use the slug instead of the team ID.

• New-GitHubTeam: Added ability to pass in the ParentTeamId (also via the pipeline) to avoid the need to query through all org teams.

• Set-GitHubTeam: Added ability to pass in the team slug (also via the pipeline) to avoid the need to query through all org teams. Similar to New-GitHubTeam, also added the ability to pass-in the ParentTeamId to avoid the full org team lookup.

• Remove-GitHubTeam: Added ability to pass in the team slug (also via the pipeline) to avoid the need to query through all org teams.

• Added Rename-GitHubTeam as a helper/wrapper on top of Set-GitHubTeam

• Added additional pipeline tests for existing functions

• Added new tests for Rename-GitHubTeam and Get-GitHubTeamMember

• Small update to formatters to capitalize and simplify headers, and simplify the display of the team parent

Issues Fixed

n/a

References

GitHub Teams API

Checklist

• You actually ran the code that you just wrote, especially if you did just "one last quick change".
• Comment-based help added/updated, including examples.
• Static analysis is reporting back clean.
• New/changed code adheres to our coding guidelines.
• Formatters were created for any new types being added.
• New/changed code continues to support the pipeline.
• Changes to the manifest file follow the manifest guidance.
• Unit tests were added/updated and are all passing. See testing guidelines. This includes making sure that all pipeline input variations have been covered.
• Relevant usage examples have been added/updated in USAGE.md.
• If desired, ensure your name is added to our Contributors list

[HowardWolosky]

/azp run PowerShellForGitHub-CI

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[HowardWolosky]

@X-Guardian - Leaving this up a day before merging it in in case you have any feedback on it.

[HowardWolosky]

/azp run PowerShellForGitHub-CI

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[X-Guardian]

I always find it annoying when the default view of an object shows label names that don't exist as properties on the object. I.e for this, if I try and read $Team.Created I will not get the desired result. I will then have to run $Team | Fl -Property * to get the actual property name created_at. Same for the updated labels below. If you want to do this, you should build the output object with these new property names.

[HowardWolosky]

This is interesting feedback that I hadn't considered, and I appreciate it. I'll make that change (and change Parent to be parent.name).

[HowardWolosky]

/azp run PowerShellForGitHub-CI

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).