Update Headers for site management panel

[candy02058912]

Fixes https://github.com/Automattic/dotcom-forge/issues/7083

Proposed Changes

• Adjust Headers so that all tabs in the site management panel look consistent

Overview

• Added header and subheader

Hosting Config

• Updated header from "Hosting" to "Hosting Config"

Monitoring

• Updated header

PHP Logs

• Added header and subheader

Server Logs

• Added header and subheader

GitHub Deployments

• Updated copy for subheader

Testing Instructions

• Go to sites dashboard and check the site management screen for atomic sites
• Make sure everything looks good

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-107547

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-107547&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-107547&env=a8c-for-agencies

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/site-management-panel-header on your sandbox.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~3915 bytes added 📈 [gzipped])

name             parsed_size           gzip_size
site-monitoring     +14155 B  (+1.4%)    +3851 B  (+1.2%)
hosting               +176 B  (+0.0%)      +64 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[fushar]

Monitoring

Should we also include the word Monitoring in the header for consistency? I'm proposing the following:

cc-ing @lucasmendes-design for review

[fushar]

I think the gap between the header and the bounding box is a bit larger than Figma design. The margin-left should be larger than the margin-top, but in this PR it is the opposite:

Figma	This PR

Can't really confirm as I am still requesting Figma Dev Mode (somehow I lost the access)

[lucasmendes-design]

About the spacing

[lucasmendes-design]

Specs can be found in this Figma file
https://www.figma.com/design/kyCC1EHKtv4qsElmlAzp5T/Flyout-panel-i2?node-id=182%3A86182&t=wtSkkUkf8Qiz6w5u-1

[lucasmendes-design]

Should we also include the word Monitoring in the header for consistency? I'm proposing the following:

Yes. I also prefer this way :)

[candy02058912]

I think the gap between the header and the bounding box is a bit larger than Figma design. The margin-left should be larger than the margin-top, but in this PR it is the opposite:

Fixed

[fushar]

Looking great!!

[lucasmendes-design]

Thanks, folks. It's perfect :)