apply h1 thickline globally

[jmealing]

As per DTO email, this is the update for the H1 globally:

• Removed gc-thickline class and css
• Modified heading base to apply the thick line styles globally

[duboisp]

We will need to check all the proper documentation + working example is also there and up to date.

[duboisp]

Move the h1 CSS and create example in this base folder: /sites/h1

Like the breadcrumb folder structure: https://github.com/wet-boew/GCWeb/tree/master/sites/breadcrumbs

1. Create a single SCSS file for the h1 style
2. Remove the old h1 style (like you did)
3. Link that newly SCSS in this main SCSS file, near the other heading style - https://github.com/wet-boew/GCWeb/blob/master/sites/theme.scss#LL35C6-L35C6
4. Create the dedicated working example (EN and FR) for the h1
5. Document in those page the version and a code sample
   a. I do think it could be version 1.0.1, a patch change considering there is not change required for the author neither the implementor. We would need to check the public versioning API to be sure. It could be seen as a Minor/Major visual change.
   b. Code sample: I do think we have a variant with the [id=wb-cont] and another one without it. And there is some variant enhance with RDFa + schema.org
6. Create the index.json-ld file (the name of the componentName need to be same as the folder name.

[duboisp]

I suggest to reorganize the documentation according to our latest documentation template prototype.

You can see how the "Change set" and "Iteration" are documented under the technical documentation section.

[delisma]

@duboisp Can you remove me and Eric as reviewers? Can you remove Jennifer as an assignee?

[duboisp]

We should clean up, which can be done on or immediately after, remove any use of "gc-thickline" in our pages.

Do we have a note about that somewhere saying that CSS class is useless because it is now the default for h1?

[GormFrank]

Pre-approved for this week provided @delisma makes the changes requested by @duboisp, which are small changes that don't affect the core purpose of this PR.

[duboisp]

Review and tested. It does work as expected.

Once this PR is merged, the following 2 actions is required immediatly after or they can be included with the release PR.

• Add the technical note about the obsoleted gc-thickline in the index.json-ld
• Regenerate the GCWeb sites assets (ex: _data/sites.json ...) to keep GCWeb web site functional.

[duboisp]

Pre-approved upon quick review of the unresolved conversation by @duboisp