VACMS-19163: changed required astrisk to after

[jv-agile6]

Description

Relates to #19163

QA steps

name: "Campaign Landing Page - Spotlight Validation"

description: QA test for ensuring required fields and validation indicators appear correctly when editing a Campaign Landing Page, and that error messages are properly linked to the corresponding fields.

steps:

• step: "Go to Tugboat instance Log in and create a new Campaign Landing Page."
  expected_result: "Login and successfully go to create a Campaign Landing Page"

  

• step: "Fill out the required fields in the Hero Banner, Why This Matters, What You Can Do, VA Benefits sections. and Selection settings"
  expected_result: "Required fields are filled out without issues."

• step: "Save as Published and save the node."
  expected_result: "Node is saved successfully."

• step: "Edit the node and enable the Spotlight section by clicking 'Enable this page segment.'"
  expected_result: "Spotlight section is enabled."

• step: "Check if the 'List of links with summaries' field is marked as required (red asterisk)."
  expected_result: "The 'List of links with summaries' field is marked with a red asterisk."

• step: "Add a Link teaser to the 'Links with summaries' field."
  expected_result: "Link teaser is added successfully."

• step: "Save the node again."
  expected_result: "Node is saved successfully without errors."

expected_behavior:

• "Required field 'List of links with summaries' should have a red asterisk."

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

GitHub Workflows (.github/workflows/*.yml)

Have you...

• pinned all affected GitHub Actions at a specific commit by SHA?
• reviewed the source code of the action at the commit you are pinning?
• confirmed that no GitHub security measures are being bypassed?
• checked for any injection of user content into protected contexts?
• reviewed Security hardening for GitHub Actions?
• reviewed GitHub Workflows?

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[dsasser]

Some nitpicks, but also seeing duplicate required indicators on the link field:

[github-actions]

Checking composer.lock changes...