chore: add linbk checking to build

[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.

[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.

[mhamilton723]

/azp run

[azure-pipelines]

No commit pushedDate could be found for PR 2034 in repo microsoft/SynapseML

[mhamilton723]

/azp run

[azure-pipelines]

No commit pushedDate could be found for PR 2034 in repo microsoft/SynapseML

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[github-actions]

Summary by GPT-4

This commit removes the GitHub action for checking dead links and adds a script to validate links during the build process. It also updates some dependencies and adds a new dependency for use-sync-external-store.

Suggestions

The changes in this PR include updating the versions of various dependencies, removing the check-dead-links.yml file, and adding a new validate_links.sh script. Overall, these changes seem to be aimed at improving the website's link validation process and keeping dependencies up-to-date. No suggestions are needed as the changes appear to be well-implemented and serve their intended purpose.

[codecov-commenter]

Codecov Report

Merging #2034 (7165855) into master (8be8fe3) will increase coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2034      +/-   ##
==========================================
+ Coverage   87.00%   87.06%   +0.06%     
==========================================
  Files         306      306              
  Lines       16068    16068              
  Branches      860      860              
==========================================
+ Hits        13980    13990      +10     
+ Misses       2088     2078      -10     

see 4 files with indirect coverage changes

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mhamilton723]

/azp run

[mhamilton723]

/azp run

[azure-pipelines]

No commit pushedDate could be found for PR 2034 in repo microsoft/SynapseML

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mhamilton723]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).