Move ADRs into history (#2246)

* add dates to history page

* remove ADRs guide

* move naming conventions non-decision into best practices

* remove disclaimer from best practices guide

* integrate ADRs into History page

* Fix final line endings

* lints

* typo

* Update docs/history.md

---------

Co-authored-by: GitHub Actions Bot <41898282+github-actions[bot]@users.noreply.github.com>

Author: joelhawksley

docs/adrs/0001-record-architecture-decisions.md

@@ -6,8 +6,6 @@ nav_order: 5
 
 # Best practices
 
-_A general guide to building component-driven UI in Rails. Consider it to be more opinion than fact._
-
 ## Philosophy
 
 ### Why ViewComponent exists
@@ -60,6 +58,10 @@ When building ViewComponents, look for opportunities to consolidate similar patt
 
 Aim to minimize the amount of single-use view code. Every new component introduced adds to application maintenance burden.
 
+### Use -Component suffix
+
+While it means class names are longer and perhaps less readable, including the -`Component` suffix in component names makes it clear that the class is a component, following Rails convention of using suffixes for all non-model objects.
+
 ## Implementation
 
 ### Avoid inheritance