Change version display for Serving and Eventing to 1.x scheme

[rhuss]

With kn version for 1.0 we still get the 'technical' version of the serving and eventing dependency like in:

Version:      v1.0.0
Build Date:   2021-11-02 19:27:09
Git Revision: a1cf5bf8
Supported APIs:
* Serving
  - serving.knative.dev/v1 (knative-serving v0.27.0)
* Eventing
  - sources.knative.dev/v1 (knative-eventing v0.27.0)
  - eventing.knative.dev/v1 (knative-eventing v0.27.0)

We detected this late in the release process and was discussed at https://knative.slack.com/archives/C02HLGQALCE/p1635874127113600 so we should change this to

Version:      v1.1.0
Build Date:   2021-11-02 19:27:09
Git Revision: a1cf5bf8
Supported APIs:
* Serving
  - serving.knative.dev/v1 (knative-serving v1.1.0)
* Eventing
  - sources.knative.dev/v1 (knative-eventing v1.1.0)
  - eventing.knative.dev/v1 (knative-eventing v1.1.0)

to avoid confusions.

[rhuss]

This can be implemented by adapting the code in

client/hack/build-flags.sh

Lines 32 to 42 in a2bb404

	version_serving=$(grep "knative.dev/serving " "${base}/go.mod" \
	| sed -s 's/.* \(v.[\.0-9]*\).*/\1/')
	version_eventing=$(grep "knative.dev/eventing " "${base}/go.mod" \
	| sed -s 's/.* \(v.[\.0-9]*\).*/\1/')
	echo "-X '${pkg}.BuildDate=${now}' \
	-X ${pkg}.Version=${version} \
	-X ${pkg}.GitRevision=${rev} \
	-X ${pkg}.VersionServing=${version_serving} \
	-X ${pkg}.VersionEventing=${version_eventing}\
	${EXTERNAL_LD_FLAGS:-}"

I think a good algo could be:

• For major.minor pick it up from the client version as given. Alternatively, use the info from the go.mod file and apply the "magic" formular of mapping 0.27 to a 1.0 baseline.
• For patchlevel pick up the patch level value from the go. mod dependency.

[kobayashi]

@rhuss Please let me know if there's anything to be added to this PR.