fix: postgres enum in schema regenerated migrations

[helmsonsen]

Description of change

added "/." to PostgresQueryRunner regex for default value retrieving to prevent regenerating migrations for enum columns with default type when the object is within a schema.

Previous Behaviour:
on any migration generation, a new migration has been created for enum default values when the object is within a named schema

Expected Behaviour:
no migration as long as the default value is not changed

A broader discussion around the issue: #3076 for which it extends the current workaround

Pull-Request Checklist

• Code is up-to-date with the master branch
• npm run lint passes with this change
• npm run test passes with this change
• This pull request links relevant issues as Fixes #0000
• There are new or updated unit tests validating the change
• Documentation has been updated to reflect this change
• The new commits follow conventions explained in CONTRIBUTING.md

[vovapilimon]

Добрый день! Когда эти правки будут доступны в мастере?

[zaro]

Is there any estimate for this, it's a blocker for updating to newer typeorm.

[pleerock]

@helmsonsen can you please update issue description - explain a bit more how it currently behaves, why and how exactly proposed solution fixes the issue?

[frostbytedata]

Did this commit truly fix the issue? I still get unnecessary migration queries added to my generated migrations with default enums. I am using TypeORM v0.3.6