ocis already does the cli flag parsing

[butonic]

The micro service.Init() function applies the options and then parses cli flags, which resets some of the defaults in micro, interfering and overriding our options.

• remove all service.Init()
• smoke test in tho browser: login, up & downloud still works
• test setting a different micro registry / log level
• test setting micro cli env vars.
• wrap service.Init() in our http and grpc services so it cannot be called accidentially.
• check if micros server.Init(), client.Init(), registry.Init() interfere in the same way ...
• maybe create ocis versions of service, client, registry...?

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[butonic]

@refs help! ;-)

[refs]

I individually tested a service (proxy) using cli flags and env variables and it behaves the same way. I'd let this go through CI, add a changelog and merge it.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[C0rby]

👍