Added data calculs during exports from postgres to mongo

[antoineludeau]

Prerequisite : postgis must be installed on postgres DB

I. Context

In the new internal main postgres DB (where we store the data from BAL with BAN-ID), we do not store data that does not come from the BAL. As a consequence, we don't have the additional data we need : fantoir code, postal code, map tiles, ...

II. Enhancement

This PR aims to calculate, during the export from postgres to mongo, the following data :

• Fantoir code on common toponyms ONLY
• Postal code on common toponyms and on addresses
• Map tiles on on common toponyms and on addresses

III. How to test

1- Download a BAL (csv)
2- Use the 'initBALIntoBAN' script of ID-Fix to push data into the BAN DB
3- Wait a few seconds for the export to be done
4- Check in your mongoDB to check on common toponyms and addresses "meta"

Exemple of an address that has those extra data calculated :

{
 ...
  "meta": {
    "geography": {
      "tiles": [
        "12/2063/1495",
        "13/4127/2991",
        "14/8254/5983"
      ],
      "x": 568642.87,
      "y": 6277331.1
    },
    "laposte": {
      "codePostal": "31100"
    }
...
}

Exemple of a common toponym :

{
...
  "meta": {
    "dgfip": {
      "fantoir": "0740"
    },
    "geography": {
      "tiles": [
        "10/516/373",
        "11/1032/747",
        "12/2064/1495",
        "13/4129/2990",
        "14/8258/5980"
      ],
      "x": 576189.38,
      "y": 6282778.42
    },
    "laposte": {
      "codePostal": "31200"
    }
...
}

[mmortier]

Le calcul du code fantoir tel qu'implémenté ici va présenter des régressions importantes sur les communes fusionnées. Le calcul doit prendre en compte les étapes de calcul et les particularités associées aux communes anciennes cf recompute-codes-voies.cjs.

[mmortier]

J'ai créé un ticket pour prendre en compte l'ancienne commune dans le calcul du code fantoir. Il sera à traiter avant d'écraser le résultat des collections legacy