Refactor Route Pages

[jtfairbank]

Description

It'd be helpful to refactor portions of the route page into their own components, similar to the home page or about-us page. There's some existing routes components in /src/components/routes but those have more to do with structuring the content than separating it. It'd be good to have separate components for each section of content, which still use the existing components to structure themselves.

CodeSee Map of relevant files.

This should pave the way for:

1. Refactoring the route page's legacy styles to use tailwind classes (see Refactor Custom CSS Classes in Stylesheets > Tailwind Classes #772)
2. Pulling more of the content out to be controlled by Forestry (our CMS) instead of hard-coded onto the page.
3. Reusable chunks of content that can be applied elsewhere (such as an FAQ).

Checklist

• Add your name to /CONTRIBUTORS.md if this is your first contribution!
• Delivery Section => Component
• Reservations Section => Component
• Frontline Section => Component
• Staging Hubs Section => Component
• Costs Section => Component
• About Pallets Section => Component

Front end feature screenshots

This refactoring shouldn't change how the content appears on the website.

Code of Conduct

• I agree to follow this project's Code of Conduct

[RabeaGleissner]

I'll start with the Delivery section!

[linds0202]

I would like to work on refactoring the 'Costs' and 'About Pallets' components

[RabeaGleissner]

Hoping to raise a PR for Frontline and Staging Hubs sections soon!

[jtfairbank]

Hey @RabeaGleissner @linds0202 thanks so much for tackling this one! If you want to continue with refactoring-related work, I'd suggest looking at #772? If figure there's enough there that y'all can split it up with @20RitikSingh?