Update to postgres 12 and postgis 3

[NickPhura]

Overview

Links to jira tickets

This PR contains the following changes

Tiny PR to update to postgres 12 and postgis 3.

The update to postgis was required, as the previous version of 2.4 had a max version of postgres that it would work with, and would throw an error if you tried to run the docker build.

This PR contains the following types of changes

• New feature (change which adds functionality)
• Bug fix (change which fixes an issue)
• Misc cleanup / Refactoring / Documentation
• Version change

Checklist

A list of items that are good to consider when making any changes.

Note: this list is not exhaustive, and not all items are always applicable.

General

• I have performed a self-review of my own code
• My code follows the style guidelines of this project
• New and existing unit tests pass locally with my changes

Code

• New files/classes/functions have appropriately descriptive names and comment blocks to describe their use/behaviour
• I have avoided duplicating code when possible, moving re-usable pieces into functions
• I have avoided hard-coding values where possible and moved any re-usable constants to a constants file
• My code is as flat as possible (avoids deeply nested if/else blocks, promise chains, etc)
• My code changes account for null/undefined values and handle errors appropriately
• My code uses types/interfaces to help describe values/parameters/etc and inform future developers

Documentation

• I have commented my code sufficiently, such that an unfamiliar developer could understand my code
• I have added/updated README's and related documentation

Tests

• I have added/updated unit tests for any new code I've added/updated
• I have added/updated Postman tests to account for any new/updated code

How Has This Been Tested?

Locally (via Docker)

Screenshots

Please add any relevant UI screenshots, if applicable.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[NickPhura]

@popkinj
I had to increase the version of postgis as a side effect of increasing the version of postgres.

I assume that should be just fine?

Postgis 2.5 or 3 were allowed options, so I just went with 3.

[anissa-agahchen]

Looks good on my end.

[popkinj]

Yeah... Definitely PostGIS 3.X.
There is actually version 3.1.0 available. But I'm not sure it's necessary for us yet.