chore: Get executable name from the command

[dwertent]

This PR enhances the FireFly CLI by making the executable name dynamic in the help messages. Instead of hardcoding the executable name, it is now loaded from the command-line arguments, allowing for dynamic help messages that reflect the actual executable name being used.

Before:

% firefly

To get started run: ff init
Optional: Set FIREFLY_HOME env variable for FireFly stack configuration path.

Usage:
  ff [command]

After:

% firefly

To get started run: firefly init
Optional: Set FIREFLY_HOME env variable for FireFly stack configuration path.

Usage:
  firefly [command]

[EnriqueL8]

I think you are missing a few such as ff start message after an ff init

[EnriqueL8]

We really need to make this usage message better

[EnriqueL8]

not part of this PR

[EnriqueL8]

You are getting a build error because of

[dwertent]

I think the build failed due to a failure in the coverage report generation, maybe we should re-run the build job (it passed last time and the only change I made was the var name)

[EnriqueL8]

I reran it and it's still failing

[EnriqueL8]

I'm quite puzzled about why we are getting a broken pipe, might some related to etcd-io/etcd#17560 or the permission in the workflow

[EnriqueL8]

This is ready to go :)

[EnriqueL8]

Looks good - Thanks!