[osci23] update installation commands (#908) (#912)

Signed-off-by: qiwen li <qiwen_li@brown.edu>
(cherry picked from commit e53ba8e)

Co-authored-by: Riley Li <71857976+MadaniKK@users.noreply.github.com>

DEVELOPER_GUIDE.md

@@ -27,7 +27,7 @@ You should have a running instance of OpenSearch Dashboards to run these tests a
 
 ### Installation
 
-To install the dependencies run 
+To install the dependencies run
 
 ```
 npm install
@@ -76,16 +76,16 @@ To run tests against a local cluster
 without security:
 
 ```
-$ yarn cypress run-without-security --spec "cypress/integration/core-opensearch-dashboards/vanilla-opensearch-dashboards/*.js"
+$ yarn cypress:run-without-security --spec "cypress/integration/core-opensearch-dashboards/vanilla-opensearch-dashboards/*.js"
 ```
 
 with security:
 
 ```
-$ yarn cypress run-with-security --spec "cypress/integration/core-opensearch-dashboards/opensearch-dashboards/*.js"
+$ yarn cypress:run-with-security --spec "cypress/integration/core-opensearch-dashboards/opensearch-dashboards/*.js"
 ```
 
-These tests run in headless mode by default. 
+These tests run in headless mode by default.
 
 And you can override certain [cypress config or environment variable](cypress.json) by applying additional cli arguments, for example to override the baseUrl and openSearchUrl to test a remote OpenSearch endpoint:
 
@@ -99,7 +99,6 @@ $ yarn cypress run --spec "cypress/integration/core-opensearch-dashboards/opense
 
 `MANAGED_SERVICE_ENDPOINT`: set to true if tests are running against managed service domains.
 
-
 ## Writing tests
 
 The testing library uses [Cypress](https://www.cypress.io/) as its testing framework and follow its high level folder structure. All tests are written under the `./cypress/integration` folder.
@@ -125,6 +124,7 @@ Tests for plugins that are not a part of the [OpenSearch Dashboards](https://git
         /plugins
             /<YOUR_PLUGIN_NAME>
 ```
+
 ### Experimental Features
 
 When writing tests for experimental features, please follow these steps.
@@ -146,16 +146,19 @@ Create a new workflow by referring to [this template](https://github.com/opensea
 To make the build repo enable your experimental feature when spinning up OSD service, make sure that you update [this file](https://github.com/opensearch-project/opensearch-build/blob/main/src/test_workflow/integ_test/service_opensearch_dashboards.py) You could either modify the start command or the yml file. To avoid a potentially long start command, it is preferred to modify the yml file to turn on the feature.
 
 ## General
+
 ### Formatting
 
 `prettier` and `ESLint` is integrated and used to standardize formatting of files, where `prettier` takes care of the code formatting and `ESLint` takes care of the code style. You can check the formatting of all files (new and existing) by running
 
 ```
 $ yarn lint
 ```
+
 and auto fix the formatting of all files (new and existing) by running
+
 ```
 $ yarn lint --fix
 ```
 
-`Husky` precommit hook is used to automatically run `yarn lint`, please fix the files according to lint result before commiting code changes (run `yarn lint --fix` for fixable errors, or manully fix code according to error messages). If you have any doubts on `ESLint` rules, feel free to [open an issue](issues).
+`Husky` precommit hook is used to automatically run `yarn lint`, please fix the files according to lint result before commiting code changes (run `yarn lint --fix` for fixable errors, or manully fix code according to error messages). If you have any doubts on `ESLint` rules, feel free to [open an issue](issues).