[DEVOPS-XXX] Use new v6 version of deploy B2C policy action

[ebronson68]

Description

• Use new v6 version of deploy B2C policy action
• Use ${{ env.[VAR] }} variable references
• Remove deprecated azureB2CProductId input

Related Issues

• Jira Issue: N/A
• Testing environment:

[github-actions]

A JIRA Issue ID is missing from your branch name! 🦄

Your branch: devops/DEVOPS-XXX/convert-to-composite-action

If this is your first time contributing to this repository - welcome!

---

Please refer to action-jira-linter to get started.

Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail.

Valid sample branch names:

‣ feature/shiny-new-feature--mojo-10'
‣ 'chore/changelogUpdate_mojo-123'
‣ 'bugfix/fix-some-strange-bug_GAL-2345'

[github-actions]

A JIRA Issue ID is missing from your branch name! 🦄

Your branch: devops/DEVOPS-XXX/convert-to-composite-action

If this is your first time contributing to this repository - welcome!

---

Please refer to action-jira-linter to get started.

Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail.

Valid sample branch names:

‣ feature/shiny-new-feature--mojo-10'
‣ 'chore/changelogUpdate_mojo-123'
‣ 'bugfix/fix-some-strange-bug_GAL-2345'

[github-actions]

A JIRA Issue ID is missing from your branch name! 🦄

Your branch: devops/DEVOPS-XXX/convert-to-composite-action

If this is your first time contributing to this repository - welcome!

---

Please refer to action-jira-linter to get started.

Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail.

Valid sample branch names:

‣ feature/shiny-new-feature--mojo-10'
‣ 'chore/changelogUpdate_mojo-123'
‣ 'bugfix/fix-some-strange-bug_GAL-2345'