Default namespace (Nuvolaris) in local installation

### Ⅰ. Issue Description

Default Namespace should be Openserverless instead of Nuvolaris

### Ⅱ. Describe what happened

The installation completes with following messages :

namespaces
**_nuvolaris_**
Logging in http://localhost:80 as _**nuvolaris**_
Successfully logged in as **_nuvolaris_**.
ok: whisk auth set. Run 'wsk property get --auth' to see the new value.
ok: whisk API host set to http://localhost:80
OpenServerless host and auth set successfully. You are now ready to use ops!
ok: updated package hello
ok: updated action hello/hello
"body": "hello, _**Nuvolaris**_"

### Ⅲ. Describe what you expected to happen

The installation should complete with the following messages :

namespaces
**_openserverless_**
Logging in http://localhost:80 as _**openserverless**_
Successfully logged in as **_openserverless_**.
ok: whisk auth set. Run 'wsk property get --auth' to see the new value.
ok: whisk API host set to http://localhost:80
OpenServerless host and auth set successfully. You are now ready to use ops!
ok: updated package hello
ok: updated action hello/hello
"body": "hello, _**Openserverless**_"

### Ⅳ. How to reproduce it (as minimally and precisely as possible)

Local installation with Docker:

1. Install ops
2. ops config minimal
3. ops setup devcluster

### Ⅴ. Anything else we need to know?

In the Tutorial (under review) are present html forms (Es: Index.html) containing relative url pointing to actions
with namespace openserverless that can be replaced with nuvolaris.

### Ⅵ. Environment:

- K8S Runtime and version:
- OPS CLI version: 0.1.0-2409121919.dev
- OS: Windows Server 2022 Version 21H2 (OS Build 20348.3207)
- Docker Version: Docker Desktop 4.38.0 (181591)

Beginne mit der Implementierung hinter `ops config minimal` und `ops setup devcluster` und verfolge dann, wo der Standard-Namespace und die Beispielantwort `hello` festgelegt werden. Überprüfe die `index.html` des Tutorials und andere HTML-Formulare auf übereinstimmende Namespace-Referenzen. Erledigt ist die Aufgabe, wenn eine lokale Docker-Installation `openserverless` durchgängig in Login-Nachrichten, der Aktionsausgabe und den Tutorial-URLs verwendet.

Vom Indexierungsmodell aus dem Issue-Text verfasst.