[Feature Request]: Remove E2E test publicationAndLibrary.js

Is your feature request related to a problem? Please describe.

We are currently migrating from E2E tests to Acceptance tests; however, some of the E2E tests are still not covered by Acceptance tests. We need to write acceptance tests covering these uncovered E2E tests and delete the corresponding E2E test.

The goal is to create a new acceptance test that covers the features currently handled by the existing E2E test.

Describe the solution (or solutions) you'd like

Write the new acceptance test and delete the existing E2E test.

Steps to follow:

1. Create a new acceptance test file in the appropriate directory.
2. Write the acceptance test based on the specifications found in the WIP Doc (Internal/External Users) linked below.
3. Add the acceptance test to acceptance.json.
4. Run the newly created test-suite locally and ensure it passes.
5. Push the code to your repo-fork.
6. Stress test the new test-suite to check for flakes. (In your Oppia repo fork, go to Actions > Stress Test Acceptance Test > Run Workflow > branch: <YOUR_FEATURE_BRANCH_NAME>, runs: 20, test-suite: <TEST_SUITE_NAME_USED_IN_ACCEPTANCE.JSON>).
7. Ensure that all jobs pass in the above workflow run.
8. Remove the corresponding E2E test file.
9. Open a PR.

Describe alternatives you've considered and rejected

No response

Additional context

No response

---

E2E Tests to be Removed

• publicationAndLibrary.js

Acceptance Tests to be Added / Updated

• [EDITED] 🟡 LO.4. Play through a lesson (WIP External Users)
  • Add first step in the acceptance test.
  • Make required changes in setup.

Documentation References

• WIP Doc (Internal Users)
• WIP Doc (External Users)
• Puppeteer Acceptance Tests Folder: [GitHub Link](https://github.com/oppia/oppia/tree/develop/core/tests/puppeteer-acceptance-tests)
• Acceptance Test Wiki: [GitHub Wiki](https://github.com/oppia/oppia/wiki/Acceptance-Tests)

[!IMPORTANT] If you want to claim this issue, strictly follow the instructions below:

1. Read the guidance (if you haven't already):
   https://github.com/oppia/oppia/wiki/Contributing-code-to-Oppia#choosing-a-good-first-issue
2. As this issue is simple, no need to explain how you’ll fix it — just provide proof you can complete it.
3. Run:

   VIDEO_RECORDING_IS_ENABLED=1 python -m scripts.run_acceptance_test --suite=<SUITE>
   

   Recordings will be saved in ../oppia_full_stack_test_video_recordings.
   Link all recordings from the latest run.
4. Use the required message template (see below).
5. For this issue, add the code changes in your message too.

Hi @jayam04 @FaithAbiola,
I would like to take up this issue.

I will update the following files:
{List files here}

Here is proof of changes:

Acceptance test 1: <Replace with acceptance test name>
{List all screen recordings}

Acceptance test 2 (if applicable):
{List all screen recordings}

File Changes
{Screenshot of file changes OR use `git diff`}

If there is no response, feel free to ping again.