[JS] fix: local debug environment variables location in teams chef bot sample

[tecton]

Linked issues

closes: #2241

Details

Provide a list of your changes here. If you are fixing a bug, please provide steps to reproduce the bug.

1. Fix bug that debugging in test tool is not working after local debugging.
   a. Clone the sample.
   b. Select "Debug (Edge)" and press "F5".
   c. Stop debugging and Select "Debug in Test Tool".
   d. The Test Tool will show authentication error.
2. Fix the outdated lines in README file.

Change details

Environment variables like bot id and password will be read from .localConfigs in npm script.
So the env file update in teamsapp.local.yml should be ".localConfigs". Writing to ".env" file will pollute the Test Tool environment.

Describe your changes, with screenshots and code snippets as appropriate

code snippets:

screenshots:

Attestation Checklist

• My code follows the style guidelines of this project

• I have checked for/fixed spelling, linting, and other errors

• I have commented my code for clarity

• I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient)

• My changes generate no new warnings

• I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:

  • Local testing
  • E2E testing in Teams

• New and existing unit tests pass locally with my changes

Additional information

Feel free to add other relevant information below

[corinagum]

Thank you for the changes! Please see comments :)

[corinagum]

@aycabas could you take a look?

[tecton]

The environment variables are loaded in npm script here.
So, I think there's no need to manually load in codes using dotenv. If ".env" is preferred filename, I could rename ".localConfigs" to ".env".

[aycabas]

Nothing major that impacts us in this PR, thanks @corinagum.

[corinagum]

Thank you for the contribution!