feat: Search Engine Optimization

[therobrob]

Description

1. feat: added sizes-attribute to images
2. feat: added meta description for news article
3. feat: added content to country list page + operator list page for better google content recognition
4. feat: added content to booking list page for better google content recognition
5. feat: added keywords to page title in hugo.yaml, because the page titles were too short
6. fix: the anchorlink copy icon is a button now
7. fix: generalized expander indicator for booking expanders
8. fix: removed page "success" from contact form
9. fix: removed h2 from navigation
10. fix: heading order startpage
11. fix: heading order booking list page
12. fix: corrected url structure folder "booking", because underscore could be problematic
13. fix: removed tags page, because we don't use it for now; it is suboptimal for seo if there is no content here
14. fix: removed canonical links, because all pages are unique
15. fix: adjusted hreflang
16. fix: Non-descriptive anchor text in internal outlinks (News No. 5)

Findings related to the meta-description are listed here: #127

Checklist

• Check the License of new pictures (non-commercial use without attribution)

The content was modified in the following languages:

• English
• German

[netlify]

✅ Deploy Preview for fipguide ready!

Name	Link
🔨 Latest commit	d6d73c2
🔍 Latest deploy log	https://app.netlify.com/projects/fipguide/deploys/6876188b7d2fb3000807fcf0
😎 Deploy Preview	https://deploy-preview-228--fipguide.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[therobrob]

It's problematic that the headings in the aside element are before the h1.

1. Using the order property would create a discrepancy between the visual representation of content and the DOM order. This negatively impacts visually impaired users who rely on assistive technology such as a screen reader.
2. Placing aside after the content is also problematic, because visually impaired users don't know there is an aside when going through the page.
3. Removing the headings from aside is problematic as well.

We should discuss, which solution fits for us.