Feature/otp 27 upgrade

[yashGojek]

Proposed Changes

• Updated OTP version to 27.0
• Fixed unable to stop application using bin/vernemq stop command( Ref. - Vanilla repo mr
• Fixed unable to connect client to vernemq (Ref. - Vanilla repo mr

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

• [] Bugfix (non-breaking change which fixes issue #XXXX)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (correction or otherwise)
• Cosmetics (whitespace, styles...)
• DevOps (Build scripts, pipelines...)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

• I have read the CODE_OF_CONDUCT.md document
• All tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if needed)
• Any dependent changes have been merged and published in related repositories
• I have updated changelog (At the bottom of the release version)
• I have squashed all my commits into one before merging

Further Comments

If this is a relatively large or complex change, kick off the discussion by
explaining why you chose the solution you did and what alternatives you
considered, etc.

[VivekPipaliya23]

can we restore the previous formatting to easily get the actual diff?

[yashGojek]

I am using default command rebar3 fmt to format. The formatting could defer because of changed rebar3 or OTP upgrade. I believe since we are upgrading both rebar3 and OTP, its best to use default config.

[VivekPipaliya23]

Can you include vanilla Vernemq PR or reference alongside the commit link where you made the specified fix/change in this PR description?