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)

Inizia dall’implementazione alla base di `ops config minimal` e `ops setup devcluster`, poi traccia dove vengono impostati il namespace predefinito e la risposta di esempio `hello`. Controlla la `index.html` del tutorial e gli altri moduli HTML alla ricerca di riferimenti corrispondenti al namespace. Il lavoro è completato quando un’installazione Docker locale usa `openserverless` in modo coerente nei messaggi di accesso, nell’output delle action e negli URL del tutorial.

Scritto dal modello di indicizzazione a partire dal testo della issue.