OCPBUGS-54670: Use PF component group for PageHeading

[logonoff]

https://issues.redhat.com//browse/CONSOLE-4492
https://issues.redhat.com/browse/OCPBUGS-54670

follow up on #14875

adopts PF PageHeader for console's main heading component.

no major UI changes should appear in this PR (e.g., create buttons appearing in a separate row as the title), except for two: operator details now have a line between the operator icon and the operator name. badges are also now placed next to the title.

fixes small a11y issue where heading actions were inside of the h1 element when it shouldn't be

[openshift-ci-robot]

@logonoff: This pull request references CONSOLE-4492 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

/hold

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [logonoff]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[logonoff]

/unhold

[logonoff]

qe review:
/assign @yapei

[openshift-ci-robot]

@logonoff: This pull request references CONSOLE-4492 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

https://issues.redhat.com//browse/CONSOLE-4492

follow up on #14875

adopts PF PageHeader for console's main heading component.

no major UI changes should appear in this PR (e.g., create buttons appearing in a separate row as the title), except for two: operator details now have a line between the operator icon and the operator name. badges are also now placed next to the title.

fixes small a11y issue where heading actions were inside of the h1 element when it shouldn't be

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[yapei]

• Check Edit YAML link and style on StorageClass, VolumeSnapshot, PersistentVolumeClaim creation page
  
• Check resource detail page when a badge is present, such as pod details page

- Check operator details page heading - Also tested against Chrome, Safari, iPhone devices

No outstanding layout issues found
/label qe-approved

[openshift-ci-robot]

@logonoff: This pull request references CONSOLE-4492 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

https://issues.redhat.com//browse/CONSOLE-4492

follow up on #14875

adopts PF PageHeader for console's main heading component.

no major UI changes should appear in this PR (e.g., create buttons appearing in a separate row as the title), except for two: operator details now have a line between the operator icon and the operator name. badges are also now placed next to the title.

fixes small a11y issue where heading actions were inside of the h1 element when it shouldn't be

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@logonoff: This pull request references Jira Issue OCPBUGS-54670, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[rhamilto]

/retest

[nicolethoen]

let's ask @nicolethoen for guidance here 👀

Did you all sort this out? I know i merged a PR in component groups which likely relates to this?

[rhamilto]

let's ask @nicolethoen for guidance here 👀

Did you all sort this out? I know i merged a PR in component groups which likely relates to this?

Yes, we did. Thank you!