update googlegroup mail list to kubernetes.io mail list

[pacoxu]

follow up of kubernetes/k8s.io#7140 @mrbobbytables

Need we also update the mailing list creation guide here as well?

community/communication/mailing-list-guidelines.md

Lines 104 to 122 in eb1417a

	## Mailing list creation
	All SIGs and WGs require two discussion groups: one for leads/chairs, and one
	for members. Subprojects that opt to have a mailing list only require one for
	members.
	### Prerequisites for creating a mailing list
	- An email account that can create Google Groups and add members external to
	your organization to a Google Group mailing list. **This might not be possible
	with your employer's email account**. You might need to use a personal email
	account.
	- At least 3 mailing list owners (leads), in addition to
	[email protected]
	- Familiarity with the [moderation guidelines] for the project and
	[moderation queue]s. Chairs should be cognizant that a new group will require
	an initial time investment moderation-wise as the group establishes itself.

. IIRC, Bob has sent an email or message somewhere about the process.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacoxu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• communication/OWNERS [pacoxu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pacoxu]

ping @mrbobbytables

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten