Start working with styling, goal: implement services & TAK content directly to UI as a 1.0 scoping decision

[benjamsf]

Why

Start working with styling working well enough for 1.0 & implementing services & TAK & TAK guides related content directly to Rasenmaeher UI v1.0 (per this issue: https://github.com/pvarki/rasenmaeher-ui/issues/1).

What

Components

Layout

• Remove layout definition from routes
• Define layout in view components instead, so that you could specify component-specific Layout props in each View
• In a view, put other components inside a Layout component for to do the thing

Navbar & Header

• Tweak navbar and header to be props for Layout so, that when you call Layout in view, you may define whether to show the user Header or Navbar
• • Header is the "Puolustusvoimat - FinnishDefenceForces" thing, that should be shown in any login related view
• • Navbar should be shown in other screens
• • If navbar is to be used, give page title and backUrl as props for Layout (which then passes them to Navbar) in any view component

Other multiuse components

• Card component to be used whenever a card with a picture and header in bottom right is used
• TextCard component for cards that contain text, add in html-react-parser for eg. adding to text
• CardsContainer component to hold cards in layout and view them in at least a remotely sane way in mobile & deskotp
• ServiceView components
• • to be ditched later when original html fragment design is implemented
• • ServiceInfoCard to be utilized in services views
• • UnfoldableCard to be utilized in ServiceTakView

Views

• As of https://github.com/pvarki/rasenmaeher-ui/issues/1, implement ServicesView, ServicesTakView and TakQuickstartView, TakUsageView directly to Rasenmaeher UI (these will be ditched at 1.1 or later when the original html fragment design is implemented
• • servicesview, servicestakview are now there

What next/Questions

• Does NOT fix ESLint errors mainly in UserManagementView
• • those are due incomplete feature implementation, need like define prop types and stuff, did not touch that as for now
• How to handle admin users and soldiers having varying access?
• • in this pr there is mock duplicates for Soldier users (SoldierServicesView, SoldierServiceTakView) as of I didn't figure that out immediately
• Related to that, Need to do the enrollment flow
• Need reach the level to be able to test mTLS create & install flow

[benjamsf]

also: did that on the top of rambo's integration branch, was that a bad idea