Useless "Way terminates on Area" warnings outside downloaded area

[mdk]

When you download a rectangle containing an area and a highway segment ending at this area OUTSIDE of the downloaded rectangle (see attached example), then the validator reports a "Way terminates on Area" warning. If you download the region where the problematic endpoint is located, additional highways will be loaded. If you run the validator again, the warning disappear.

In general, the validator should never report errors, warnings or hints outside the downloaded bounding boxes which disappear when you also download the area, where the problem was reported.

More general: When does it make sense to report problems outside the downloaded area?

[mdk]

Wrong "Barrier entrance not set on a barrier" warning

[mdk]

The second attachment is a similar problem with barriers.

[simon04]

In 6639/josm:

fix #9544 - Skip nodes outside of download area for BarriersEntrances and WayConnectedToArea validation tests

[aceman]

Yes, I also notice bogus warnings with bridge relations that have some members not fully loaded. Let's see if this patch fixes those too.