The only way I managed to get this to stop spitting out SQL was to add the property at a code level.
private Properties additionalProperties(){
var properties = new Properties();
properties.setProperty("hibernate.show_sql", "false");
properties.setProperty("hibernate.dialect", "org.hibernate.dialect.PostgreSQLDialect");
return properties;
}
The portion containing the dialect was already there and I added the show_sql - I am not sure why the properties file was not doing this, perhaps
em.setJpaProperties(additionalProperties());
is overriding the properties set in the application properties file (which makes sense as it is a "set" call). Upon attempting to move the these values to the properties file and stop setting them in the config file the properties still weren't being set.
I am leaving this here as an explanation for anyone else that might have gone down the same rabbit hole as myself - should I make further progress on setting the values in the properties file I will share it here as well.
Thanks to everyone that reviewed this questions and those that tried to help