bufr-to-bufr pipeline does not match on tsi

[maaikelimper]

As reported by Iran, they have registered station wsi=0-364-0-40755 with tsi=40755 in their wis2box station metadata

But when they ingest data for this station it fails:

This is due to the get_valid_station-function in station.py ignoring the input tsi:
https://github.com/wmo-im/wis2box/blob/main/wis2box-management/wis2box/metadata/station.py#L356-L372

@efucile I'm trying to understand if we implemented this on purpose, to force users to encode correct wsi in their input-bufr ?

On the other hand the bufr-to-bufr pipeline is recreating the wis2box with the wsi provided from the station-metadata, so there is no reason to fail to bufr-ingestion for this.

[maaikelimper]

The same issue was reported by Barbados, it seems to be a common case, so I prepare a fix to allow the bufr-to-bufr pipeline to match on tsi and encode the wigos-station-identifier provided by the station metadata.