feat(tup-cms): accent colors & new ui patterns & ui demo fixes

[wesleyboar]

Overview & Changes

• Update TUP CMS image.
• Set TACC CMS accent colors.
• Add many patterns (from Core-Styles via CMS﹡).

^{﹡Porting TACC/Core-Styles updates to TACC/tup-ui:/libs/core-styles is tedious and redundant. I seek a better solution, perhaps replace latter with former.}

Related

• includes https://github.com/TACC/Core-Styles/releases/tag/v0.11.0
• includes feat(core-styles): v0.10.0 Core-CMS#567
• includes fix: pattern demo repair suite Core-CMS#568
• includes feat(core-styles): v2 Core-CMS#569
• includes FP-1878 (via its many PRs)

Testing & UI

Test all these:

1. docs(components): tup-354 bootstrap.modal; assets, loremipsum Core-Styles#51 *
2. docs(components): tup-356 bootstrap.form Core-Styles#52 *
3. docs(components): tup-356 bootstrap.container Core-Styles#54 *
4. feat: tup-355 links (redo #57) Core-Styles#58 *
5. feat(c-button): do not show <a> tag button for --as-link Core-Styles#59 *
6. feat: x-link, used by c-button--as-link & links Core-Styles#60 *
7. feat(elements): fp-1878 table pattern Core-Styles#64
8. feat(objects): o-table, o-fixed-header-table, o-flex-item-table-wrap Core-Styles#68

^{* From https://github.com/TACC/Core-Styles/releases/tag/v0.10.0.}

[wesleyboar]

I heavily tested this. I am merging it so (A) I can use latest Core-Styles in CMS and tup-ui off of one branch (i.e. #70's) more obviously, and (B) I can begin to point developers to documented patterns.

_{A designer (C.J.) tested this, and liked it. Another designer (M.S.) is already keen on it. A third designer (H.P.) supports the concept in any form.}