Make integration test less synthetic

[Kostov6]

What would you like to be added:
An integration test that is an example how docforge's own documentation(/docs) resources could be bundled into a hugo website structure

The integration test should cover:

• proper link resolution
• frontmatter
• ...

Why is this needed / describe a real-world scenario:
Current integration test is very synthetic and is hard to understand. Let's make it instead reflect a real world scenario - how docforge's own documentation resources can be bundled into a hugo website structure. This way we are forced to use and document our own features.

How to categorize this?:

/kind enhancement
/priority 3

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close

/lifecycle rotten