fix: use channel.address instead of id

[Souvikns]

Description

This small fix updates channel.address() instead of channel.id() in mqtt.

Related issue(s)

Fixes #581

[coveralls]

Pull Request Test Coverage Report for Build 6904144969

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 67.034%

---

Totals
Change from base Build 6879694135:	0.0%
Covered Lines:	359
Relevant Lines:	472

---

💛 - Coveralls

[KhudaDad414]

Hey @Souvikns , can you also make sure that when we receive a message, we pass the channel name to the message when it is created not channel address, since glee will verify the channel name.

[Souvikns]

Yeah Looks like we are doing it

[KhudaDad414]

When we receive a message and create the message here:

    return new GleeMessage({
      payload: packet.payload,
      headers,
      channel: packet.topic,
    })
  }

we use the channel address (which is topic) but glee expects to receive the channel id.
I mean we should change this code to create the message with the channel id not channel address here.
If you run the current code with an example, it will fail.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.1% Duplication

[KhudaDad414]

LGTM!

[Souvikns]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 0.30.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[derberg]

@Souvikns you will need to manually update CLI -> https://github.com/asyncapi/cli/blob/master/assets/create-glee-app/templates/tutorial/package.json#L19 as the bumper that we use, is capable to updating just one dependency in given repo, and first on the list that it takes into account is the default one only