Merging the 7.6.1 testing branch into our VTechWorks dev branch

Merge conflicts were resolved in:

item-page-title-field.component.html
  upstream heading level accessibility fix plus local customization
  to allow italics in item titles

metadata-field-wrapper.component.html
  upstream heading level accessibility fix plus local customization
  to use "Persistent Identifier" as the URI label

To fix build issues with the merged code, additional changes were made to:

angular.json - remove comment from standard JSON format file
i18n/en.json - add missing comment after label definition

The error with the missing comment appears to have occured due to a difference in opinion and/or expectations with whether the last item in a comma separated list should/does have a trailing comma.

.github/disabled-workflows/pull_request_opened.yml

-# This workflow runs whenever a new pull request is created
-# TEMPORARILY DISABLED. Unfortunately this doesn't work for PRs created from forked repositories (which is how we tend to create PRs).
-# There is no known workaround yet. See https://github.community/t/how-to-use-github-token-for-prs-from-forks/16818
-name: Pull Request opened
-
-# Only run for newly opened PRs against the "main" branch
-on: 
-  pull_request:
-    types: [opened]
-    branches: 
-      - main
-
-jobs:
-  automation:
-    runs-on: ubuntu-latest
-    steps:
-    # Assign the PR to whomever created it. This is useful for visualizing assignments on project boards
-    # See https://github.com/marketplace/actions/pull-request-assigner
-    - name: Assign PR to creator
-      uses: thomaseizinger/assign-pr-creator-action@v1.0.0
-      # Note, this authentication token is created automatically
-      # See: https://docs.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token
-      with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
-      # Ignore errors. It is possible the PR was created by someone who cannot be assigned
-      continue-on-error: true