[Website] add linkedIn case-study

[bullet03]

• add linkedIn case-study with related files

---

before:

after:

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[dariabezkorovaina]

@aaltay we've prepared this draft PR for the LinkedIn case study, but for the past 6 hours, the staging has been failing to build for some reason... Can you please help with this?

[aaltay]

@liferoad - would it be possible for someone in the team to look at the failing beam_PreCommit_Whitespace . I looked at the logs, it seems to be failing because it is failing to setup the dependencies to run whitespace check and not because it is failing the whitespace check.

Reference to failed run: https://github.com/apache/beam/actions/runs/6536879246/job/17749540379?pr=28988

[aaltay]

Run Whitespace PreCommit

[liferoad]

I doubt this is related to this PR. cc @damccorm

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @robertwb added as fallback since no labels match configuration

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control

[damccorm]

I doubt this is related to this PR. cc @damccorm

Whitespace is back to green - https://github.com/apache/beam/actions/workflows/beam_PreCommit_Whitespace.yml?query=event%3Aschedule - there were several issues around checking for the new error of pip and downloading it that show up in the failures, guessing it was a transient pip remote issue.

Regardless, should be safe to ignore

[bullet03]

R: @aaltay , could you, please help with the review of current PR?

[aaltay]

Looks great, thank you!

[aaltay]

Published: https://beam.apache.org/case-studies/linkedin/