Fix STDOUT logger bug

[Coder3333]

Description

Fixed a bug that prevented the STDOUT logger from ever being used, because the GetLogPath method would change the input logPath, which would prevent ReconfigureEasyLogging from recognizing the request for STDOUT.

Checklist

• Code compiles correctly
• Code is formatted according to Coding Conventions
• Created tests which fail without the change (if possible)
• All tests passing (dotnet test)
• Extended the README / documentation, if necessary
• Provide JIRA issue id (if possible) or GitHub issue id in PR name

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9511947	Assigned	ODBC Connection String	3d78011	Snowflake.Data.Tests/UnitTests/SFOktaTest.cs	View secret

🛠 Guidelines to remediate hardcoded secrets

The above secret(s) have been detected in your PR. Please take an appropriate action for each secret:

• If it’s a true positive, remove the secret from source code, revoke it and migrate to a secure way of storing and accessing secrets (see http://go/secrets-and-code). Once that’s done, go to the incidents page linked in the “GitGuardian id” column (log in using SnowBiz Okta) and resolve the incident.
• If it’s a false positive, go to the incidents page linked in the “GitGuardian id” column (log in using SnowBiz Okta) and ignore the incident.
• If you didn't add this secret - and only then - you may ignore this check as it's non-blocking. If you did add the secret and you ignore this check, you'll be assigned a "Security Finding" ticket in Jira in a few days.

Note:

• A secret is considered leaked from the moment it touches GitHub. Rewriting git history by force pushing or other means is not necessary and doesn’t change the fact that the secret has to be revoked.
• This check has a “Skip: false positive” button. Don’t use it. It will mark all detected secrets as false positives but only in the context of this specific run - it won’t remember this action in subsequent check runs.

If you encounter any problems you can reach out to us on Slack: #gitguardian-secret-scanning-help

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[Coder3333]

I have read the CLA Document and I hereby sign the CLA

[sfc-gh-knozderko]

I'm closing this PR because I did some small changes and added a test in this PR: #1087
which is already merged.

Thanks for your contribution.