Additional features for the Map component

### Description

After talking with owners (Rana kommune, DIHE) of services that utilize mapswhere the user is supposed to draw and send in geometries, it seems there are a lot of potential for expanding the features of the Map component.

Some of the more wanted features are:
- Restricting areas from being drawn on.
- For example by the service-owner pre-filling the map with a geometry which restricts drawing over
- This will prevent needs of forms needing to be re-submitted due to invalid drawings.
- Related to the previous point, validation of where the user is drawing could be useful.
- Could be both warnings and hard validations
- A mentioned use-case is warning a user when they are drawing close to another object, (ex. marking the wanted placement of a well 50 meters within a septic tank)
- Letting the end-user choose between pre-loaded geometries on a map and only sending in the chosen geometries.
- A use-case for this is when one is applying for "motorferdsel" and needs to chose a drivable path on the map. The service-owner can then pre-load the map with "approved" drivable paths, and the user then selects the paths that are relevant for their driving needs.
- An addition to the previous point that is worth investigating is if it is possible to automatically determine the shortest path between your destination and the starting point, and choose the appropriate geometry paths for you.
- In this case the user should be able to edit the automatic suggestion.

### Additional Information

_No response_

Start at the Map component and inspect its existing geometry-drawing and pre-loaded geometry entry points. The issue lists several candidate capabilities—restricted drawing, validation, geometry selection, and shortest paths—so the scope should first be split and agreed with maintainers. No files, tests, or completion criteria are identified.

Written by the indexing model from the issue text.