Config options like --port, --config are ignored since v4.1.1

[bugra9]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.

Issue Description

Can't start parse-dashboard with options like --port, --config.

• parse-dashboard v4.1.0 is dependent on commander.js v6.2.1
• parse-dashboard v4.1.1 is dependent on commander.js v9.0.0.

https://github.com/tj/commander.js/releases/tag/v7.0.0
Breaking: options are stored safely by default, not as properties on the command (tj/commander.js#1409)

• this especially affects accessing options on program, use program.opts()
• revert behaviour with .storeOptionsAsProperties()

Steps to reproduce

./node_modules/.bin/parse-dashboard --port 4041

Actual Outcome

The dashboard is now available at http://0.0.0.0:4040/

Expected Outcome

The dashboard is now available at http://0.0.0.0:4041/

Environment

Dashboard

• Parse Dashboard version: 4.4.1
• Browser (Safari, Chrome, Firefox, Edge, etc.): Firefox
• Browser version: 99.0.1

Server

• Parse Server version: 5.2.1
• Operating system: Arch Linux
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local

Database

• System (MongoDB or Postgres): MongoDB
• Database version: 5.0.8
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Local

Logs

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[piyushbeli]

It also does not take the config file into the consideration. that said it will always try to run with default settings.

[mtrezza]

Thanks for pointing this out, would you want to open a PR and try to fix this?

[mtrezza]

Closing via #2113