Add mapFeature field to link quest objectives to map nodes

[kirillsst]

Summary

Adds an optional mapFeature field to quest objectives, enabling direct linking from quest pages to interactive map features.

This is a proof-of-concept implementation for a_lay_of_the_land.json quest, linking two objectives to their corresponding Spaceport map features:

• "Find the shipping notes in the foreman's office" → feature 52
• "Locate the scanners in the Flight Control office of Control Tower A6" → feature 53

Format

The field is optional and only added to objectives that have a corresponding map location:

{
  "en": "Find the shipping notes in the foreman's office",
  "mapFeature": { "map": "the_spaceport", "feature": 52 },
  ...
}

This allows the frontend to construct links like:
/api/maps/the-spaceport?feature=52

Next steps

If this approach looks good, the same field can be added to other quests that reference specific map locations.

Closes #99

[baschny]

I find the idea cool! I would not mix the map links in mids of the translations. There needs to be a structure here, like:

  "objectives": [
    ...
    {
      "description": {
        "da": "Find fragtsedlerne på formandens kontor",
        "de": "Finde die Versandnotizen im Büro des Vorarbeiters.",
        "en": "Find the shipping notes in the foreman’s office",
        ...
      },
      "mapFeature": {
        "map": "the_spaceport",
        "feature": 52
      }
  }

That of course requires a change in the structure and people using will have to adapt to that, but I think currently there is no flexibility inside each step of the objectives, and we might want to add more data to each step in future (i.e. the "Deliver" => "itemId" etc).

What do you think @mattmarcin ??

[baschny]

The mapFeature might even be an array, there might be multiple locations for one objective.

[uilson]

dont forget to account for different parts of the mission in different maps too, i can see this becoming very convoluted with all the data.