VACMS-18659: Update clp node to be able to use url for field links

[chriskim2311]

Summary

For this PR we are introducing URL paths when available for CLP field links when referencing internal links. We will defer back to URI if there is no URL available.

Changes for field links are made for the following fields in CLPs:
What you can do
Spotlight
Stories

Related issue(s)

department-of-veterans-affairs/va.gov-cms#18659

Testing done

Tested in tugboat instance

CMS: https://main-jk4uouhulv1tbvo6a4fqxpyyjvjnazmf.ci.cms.va.gov/initiatives/prepare-for-vas-secure-sign-in-changes

Review Instance : https://main-jk4uouhulv1tbvo6a4fqxpyyjvjnazmf.ci.cms.va.gov/initiatives/prepare-for-vas-secure-sign-in-changes?_format=static_html

Screenshots

CMS for Stories Field Link Node

Stories Field Link URL

Stories Field Link graphQL

CMS for What you can do Field Link Node

What you can do Field Link URL and graphQL

What areas of the site does it impact?

CLPs

Acceptance criteria

• Linked node IDs direct to the correct live VA.gov page or trigger a 403

Quality Assurance & Testing

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Linting warnings have been addressed
• Documentation has been updated (link to documentation *if necessary)
• Screenshot of the developed feature is added
• Accessibility testing has been performed

Error Handling

• Browser console contains no warnings or errors.
• Events are being sent to the appropriate logging solution
• Feature/bug has a monitor built into Datadog or Grafana (if applicable)

[laflannery]

@chriskim2311 I'm building this on my tugboat because I want to test something else but for right now I have one question on the What you can do section:

• The second 2 items have full URLs in the CMS but on the Front end they are going to dev.va URLs, that seems weird. Wouldn't they go to the main prod site because of the URL in Drupal?
  CMS
  

Front end

[laflannery]

@chriskim2311 My tugboat eventually publishing and I see no other issues. If we can just investigation my previous question and figure out why it's pulling dev instead of the full URL that's the only issue I see

[eselkin]

code/queries lgtm

[randimays]

LGTM!