chore: remove secret scanner

[mhamilton723]

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

Briefly describe the changes included in this Pull Request.

How is this patch tested?

• I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

• No. You can skip this section.
• Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

• No. You can skip this section.
• Yes. Make sure you have added samples following below steps.

1. Find the corresponding markdown file for your new feature in website/docs/documentation folder.
   Make sure you choose the correct class estimators/transformers and namespace.
2. Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
3. Make sure the DocTable points to correct API link.
4. Navigate to website folder, and run yarn run start to make sure the website renders correctly.
5. Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
6. Make sure the WebsiteSamplesTests job pass in the pipeline.

[mhamilton723]

/azp run

[github-actions]

Hey @mhamilton723 👋!
Thank you so much for contributing to our repository 🙌.
Someone from SynapseML Team will be reviewing this pull request soon.

We use semantic commit messages to streamline the release process.
Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix.
This helps us to create release messages and credit you for your hard work!

Examples of commit messages with semantic prefixes:

• fix: Fix LightGBM crashes with empty partitions
• feat: Make HTTP on Spark back-offs configurable
• docs: Update Spark Serving usage
• build: Add codecov support
• perf: improve LightGBM memory usage
• refactor: make python code generation rely on classes
• style: Remove nulls from CNTKModel
• test: Add test coverage for CNTKModel

To test your commit locally, please follow our guild on building from source.
Check out the developer guide for additional guidance on testing your change.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[github-actions]

Summary by GPT-4

The code removed in this commit is a test called "Scan codebase for secrets". This test scans the codebase for any secrets (like passwords, API keys, etc.) that should not be present in the code. It does this by checking file names and contents against a list of regular expressions that match common secret patterns.

The test first excludes certain files and directories from the scan, such as images and build artifacts. Then, it reads the list of regular expressions from a file specified by Secrets.SecretRegexpFile. For each file in the codebase, it checks if its name or any of its lines match any of the regular expressions. If there are any matches, the test fails and reports the issues found.

By removing this test, the codebase will no longer be checked for secrets during testing. This could potentially lead to sensitive information being accidentally committed to the repository.

Suggestions

No suggestions are needed as the changes in this PR seem to be clear and straightforward.

[codecov-commenter]

Codecov Report

Merging #2048 (7b7c58c) into master (8f794c8) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2048      +/-   ##
==========================================
- Coverage   87.05%   86.99%   -0.06%     
==========================================
  Files         306      306              
  Lines       16063    16063              
  Branches      852      852              
==========================================
- Hits        13983    13974       -9     
- Misses       2080     2089       +9     

see 3 files with indirect coverage changes