fix: Always run "kong migrations up"

[lenny-goodell]

This ensures any missing migration are run and doesn't hurt if there are none. No need to run kong migrations list

fixes #4171

Signed-off-by: Leonard Goodell leonard.goodell@intel.com

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md

PR Checklist

Please check if your PR fulfills the following requirements:

• I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
• I am not introducing a new dependency (add notes below if you are)
• I have added unit tests for the new feature or bug fix (if not, why?) N/A
• I have fully tested (add details below) this the new feature or bug fix (if not, why?)
• I have opened a PR for the related docs change (if not, why?) N/A

Testing Instructions

Run Kamakura secure stack compose file
Get API Gateway token and verify API Gateway is functional
Stop (down) the services w/o clearing volumes
Run latest WIP secure stack compose file with Kong changed to version 2.8 and restart: always commented out.
Verify Kong remains running and the API Gateway is functional using the same token from the Kamakura stack
Stop (down) the services w/o clearing volumes
Run latest WIP secure stack compose file with Kong changed to version 2.8 and restart: always commented out.
Verify Kong still remains running and the API Gateway still is functional using the same token from the Kamakura stack

New Dependency Instructions (If applicable)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.1% Duplication