Fix godocs autoformatting from upgrading to go 1.19

[Jefftree]

What happened?

Reference Comment: #111254 (comment)

Based on the diff: https://github.com/kubernetes/kubernetes/pull/111254/files, there are a couple areas where indentations are turned into paragraphs, indentations are turning regular comments into code blocks, etc.

I think there are a couple things we need to do (could be in separate PRs):

1. Scan the original PR (see above) and fix the indentations in places where a paragraph is not supposed to occur. A good example is https://github.com/dims/kubernetes/blob/a9593d634c6a053848413e600dadbf974627515f/cmd/kube-apiserver/app/testing/testserver.go#L96-L99
2. Some indentations should be changed into lists, eg: https://github.com/dims/kubernetes/blob/a9593d634c6a053848413e600dadbf974627515f/pkg/apis/core/types.go#L3222-L3226
3. Unrelated to the previous PR, scan the k8s types and reformat bullet points using * to use -. go1.19 does not recognize * as bullet points. For example: https://github.com/dims/kubernetes/blob/a9593d634c6a053848413e600dadbf974627515f/staging/src/k8s.io/api/core/v1/types.go#L495-L496
4. Ensure our swagger doc generation properly supports the new list format Keep the list style for generated swagger doc #111505

I hope this roughly captures the intent of the comment by liggitt.
/cc @liggitt
/cc @dims

/help

What did you expect to happen?

See above

How can we reproduce it (as minimally and precisely as possible)?

See above

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

@Jefftree:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

What happened?

Reference Comment: #111254 (comment)

Based on the diff: https://github.com/kubernetes/kubernetes/pull/111254/files, there are a couple areas where indentations are turned into paragraphs, indentations are turning regular comments into code blocks, etc.

I think there are a couple things we need to do (could be in separate PRs):

1. Scan the original PR (see above) and fix the indentations in places where a paragraph is not supposed to occur. A good example is https://github.com/dims/kubernetes/blob/a9593d634c6a053848413e600dadbf974627515f/cmd/kube-apiserver/app/testing/testserver.go#L96-L99
2. Some indentations should be changed into lists, eg: https://github.com/dims/kubernetes/blob/a9593d634c6a053848413e600dadbf974627515f/pkg/apis/core/types.go#L3222-L3226
3. Unrelated to the previous PR, scan the k8s types and reformat bullet points using * to use -. go1.19 does not recognize * as bullet points. For example: https://github.com/dims/kubernetes/blob/a9593d634c6a053848413e600dadbf974627515f/staging/src/k8s.io/api/core/v1/types.go#L495-L496
4. Ensure our swagger doc generation properly supports the new list format Keep the list style for generated swagger doc #111505

I hope this roughly captures the intent of the comment by liggitt.
/cc @liggitt
/cc @dims

/help

What did you expect to happen?

See above

How can we reproduce it (as minimally and precisely as possible)?

See above

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@Jefftree: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[yangjunmyfm192085]

/assgin @sanwishe

[Jefftree]

/sig docs

[flynnhandley]

/assign

[Darshnadas]

/assign

[Darshnadas]

I won't be able to work on this, due to other work commitments. Hence, unassigning myself, anyone feel free to take upon this issue.

[liggitt]

Created #114559 to resolve this