Bump version to v3.7.0

[rm3l]

What type of PR is this:

What does this PR do / why we need it:

Which issue(s) this PR fixes:
Relates to #6413

PR acceptance criteria:

• Unit test

• Integration test

• Documentation

How to test changes / Special notes to the reviewer:

[netlify]

✅ Deploy Preview for odo-docusaurus-preview ready!

Name	Link
🔨 Latest commit	1a11d7d
🔍 Latest deploy log	https://app.netlify.com/sites/odo-docusaurus-preview/deploys/63ecc4022159b500077047fe
😎 Deploy Preview	https://deploy-preview-6596--odo-docusaurus-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[odo-robot]

OpenShift Unauthenticated Tests on commit e983fec finished successfully.
View logs: TXT HTML

[odo-robot]

NoCluster Tests on commit e983fec finished successfully.
View logs: TXT HTML

[odo-robot]

Unit Tests on commit e983fec finished successfully.
View logs: TXT HTML

[odo-robot]

Validate Tests on commit e983fec finished successfully.
View logs: TXT HTML

[odo-robot]

Kubernetes Tests on commit e983fec finished successfully.
View logs: TXT HTML

[odo-robot]

Windows Tests (OCP) on commit e983fec finished with errors.
View logs: TXT HTML

[rm3l]

Expected
      <*url.Error | 0xc00038af30>: {
          Op: "Post",
          URL: "http://127.0.0.1:61285/api/newuser",
          Err: <*errors.errorString | 0xc00007c130>{s: "EOF"},
      }
  to be nil
  In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/3255/tests/e2escenarios/e2e_test.go:306

  There were additional failures detected after the initial failure.  Here's a summary - for full details run Ginkgo in verbose mode:
    [FAILED] in [AfterEach] at C:/Users/Administrator.ANSIBLE-TEST-VS/3255/tests/helper/helper_filesystem.go:49
------------------------------


Summarizing 1 Failure:
  [FAIL] E2E Test starting with non-empty Directory add Binding [It] should verify developer workflow of using binding as env in innerloop
  C:/Users/Administrator.ANSIBLE-TEST-VS/3255/tests/e2escenarios/e2e_test.go:306

/override windows-integration-test/Windows-test

Flaky E2E test - following up in #6582

[odo-robot]

OpenShift Tests on commit e983fec finished successfully.
View logs: TXT HTML

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: windows-integration-test/Windows-test

In response to this:

Expected
     <*url.Error | 0xc00038af30>: {
         Op: "Post",
         URL: "http://127.0.0.1:61285/api/newuser",
         Err: <*errors.errorString | 0xc00007c130>{s: "EOF"},
     }
 to be nil
 In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/3255/tests/e2escenarios/e2e_test.go:306

 There were additional failures detected after the initial failure.  Here's a summary - for full details run Ginkgo in verbose mode:
   [FAILED] in [AfterEach] at C:/Users/Administrator.ANSIBLE-TEST-VS/3255/tests/helper/helper_filesystem.go:49
------------------------------


Summarizing 1 Failure:
 [FAIL] E2E Test starting with non-empty Directory add Binding [It] should verify developer workflow of using binding as env in innerloop
 C:/Users/Administrator.ANSIBLE-TEST-VS/3255/tests/e2escenarios/e2e_test.go:306

/override windows-integration-test/Windows-test

Flaky E2E test - following up in #6582

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.

[odo-robot]

Kubernetes Docs Tests on commit 96e9adf finished successfully.
View logs: TXT HTML

[feloy]

You would need to update some doc to make the tests pass, for example:

 Expected
      <string>:   strings.Join({
        	... // 93 identical bytes
        	"me my-nodejs-app --starter nodejs-angular-starter\n__\n/  \\__     ",
        	"Initializing a new component\n\\__/  \\\n/  \\__/    odo version: v3.",
      - 	"6",
      + 	"7",
        	".0\n\\__/\n\n✓  Downloading devfile from \"https://registry.devfile",
        	".io/devfiles/nodejs-angular\" [1s]\n✓  Downloading starter proje",
        	... // 249 identical bytes
        }, "")
      
  to be empty
  In [It] at: /go/odo_1/tests/documentation/command-reference/doc_command_reference_init_test.go:123

[rm3l]

You would need to update some doc to make the tests pass, for example:

 Expected
      <string>:   strings.Join({
        	... // 93 identical bytes
        	"me my-nodejs-app --starter nodejs-angular-starter\n__\n/  \\__     ",
        	"Initializing a new component\n\\__/  \\\n/  \\__/    odo version: v3.",
      - 	"6",
      + 	"7",
        	".0\n\\__/\n\n✓  Downloading devfile from \"https://registry.devfile",
        	".io/devfiles/nodejs-angular\" [1s]\n✓  Downloading starter proje",
        	... // 249 identical bytes
        }, "")
      
  to be empty
  In [It] at: /go/odo_1/tests/documentation/command-reference/doc_command_reference_init_test.go:123

Well, this is expected on one hand, but on the other hand, should we really update the docs at this point (at least until the 3.7.0 binaries are available)? Otherwise, this means that the docs will display 3.7.0, but this version is not published yet.

Anyway, those are "just" sample outputs, so I'll make the changes in the docs.
All tests should pass on the commit that will be tagged.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[rm3l]

Expected
      <*url.Error | 0xc0006c9800>: {
          Op: "Post",
          URL: "http://127.0.0.1:63288/api/newuser",
          Err: <*errors.errorString | 0xc00007c130>{s: "EOF"},
      }
  to be nil
  In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/3256/tests/e2escenarios/e2e_test.go:306

  There were additional failures detected after the initial failure.  Here's a summary - for full details run Ginkgo in verbose mode:
    [FAILED] in [AfterEach] at C:/Users/Administrator.ANSIBLE-TEST-VS/3256/tests/helper/helper_filesystem.go:49
------------------------------


Summarizing 1 Failure:
  [FAIL] E2E Test starting with non-empty Directory add Binding [It] should verify developer workflow of using binding as env in innerloop
  C:/Users/Administrator.ANSIBLE-TEST-VS/3256/tests/e2escenarios/e2e_test.go:306

Ran 7 of 7 Specs in 208.777 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 0 Skipped

/override windows-integration-test/Windows-test

Flaky E2E test - following up in #6582

[openshift-ci]

@rm3l: Overrode contexts on behalf of rm3l: windows-integration-test/Windows-test

In response to this:

Expected
     <*url.Error | 0xc0006c9800>: {
         Op: "Post",
         URL: "http://127.0.0.1:63288/api/newuser",
         Err: <*errors.errorString | 0xc00007c130>{s: "EOF"},
     }
 to be nil
 In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/3256/tests/e2escenarios/e2e_test.go:306

 There were additional failures detected after the initial failure.  Here's a summary - for full details run Ginkgo in verbose mode:
   [FAILED] in [AfterEach] at C:/Users/Administrator.ANSIBLE-TEST-VS/3256/tests/helper/helper_filesystem.go:49
------------------------------


Summarizing 1 Failure:
 [FAIL] E2E Test starting with non-empty Directory add Binding [It] should verify developer workflow of using binding as env in innerloop
 C:/Users/Administrator.ANSIBLE-TEST-VS/3256/tests/e2escenarios/e2e_test.go:306

Ran 7 of 7 Specs in 208.777 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 0 Skipped

/override windows-integration-test/Windows-test

Flaky E2E test - following up in #6582

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.