[Themes-1204] Added color to full-author-bio and short-author-bio headings

[malavikakoppula]

Description

The Full bio block role connect text needs to be updated to be a text-color alias token. So the color of the font doesn’t change.

Jira Ticket

• THEMES-1204

Acceptance Criteria

• Update the font color of the author role and the connect text as the text-color in the Full author bio block.
• Update the font of the author’s name in the short bio block to be the primary color.

Test Steps

1. Checkout this branch git checkout THEMES-1204
2. Run fusion repo with linked blocks npx fusion start -f -l @wpmedia/author-bio-block,@wpmedia/full-author-bio-block
3. Add content api _id: 7E3ZKVJFVJBNBAWIKNENACWWTA
4. inspect for short-author-bio author name to be color-primary and, full-author-bio role and social-header to be text-color alias token

Effect Of Changes

Before

After

Dependencies or Side Effects

• Feature pack pr for local development: https://github.com/WPMedia/arc-themes-feature-pack/pull/508

Author Checklist

The author of the PR should fill out the following sections to ensure this PR is ready for review.

• Confirmed all the test steps a reviewer will follow above are working.
• Confirmed there are no linter errors. Please run npm run lint to check for errors. Often, npm run lint:fix will fix those errors and warnings.
• Ran this code locally and checked that there are not any unintended side effects. For example, that a CSS selector is scoped only to a particular block.
• Confirmed this PR has reasonable code coverage. You can run npm run test:coverage to see your progress.
  • Confirmed this PR has unit test files
  • Ran npm run test, made sure all tests are passing
  • If the amount of work to write unit tests for this change are excessive,
    please explain why (so that we can fix it whenever it gets refactored).
• Confirmed relevant documentation has been updated/added.

Reviewer Checklist

The reviewer of the PR should copy-paste this template into the review comments on review.

• Linting code actions have passed.
• Ran the code locally based on the test instructions.
  • I don’t think this is needed to be tested locally. For example, a padding style change (storybook?) or a logic change (write a test).
• I am a member of the engine theme team so that I can approve and merge this. If you're not on the team, you won't have access to approve and merge this pr.
• Looked to see that the new or changed code has code coverage, specifically. We want the global code coverage to keep on going up with targeted testing.

[blakeganderson]

LGTM

[malavikakoppula]

Marking as do not merge since we want this in the next release, not 2.2.0.

The base branch was changed.

[malavikakoppula]

Marking as do not merge since we want this in the next release, not 2.2.0.

This is releasing as part of 2.2.1