fix: use IssueReporting

[grdsdev]

What kind of change does this PR introduce?

Fix

What is the current behavior?

Some issues that needs action from developers are reported using a warning log, which may be lost if a logger isn't attached.

What is the new behavior?

Use IssueReporting lib we already depend on and are using on some places in everywhere the developer is doing something wrong and should action on it.

Additional context

The reportIssue call is no-op in RELEASE builds, but triggers a "purple warning" in Xcode in DEBUG builds, something similar to a breakpoint that doesn't stop execution.

[coveralls]

Pull Request Test Coverage Report for Build 18556248448

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 5 of 23 (21.74%) changed or added relevant lines in 2 files are covered.
• 54 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.9%) to 76.755%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
Sources/Realtime/RealtimeChannelV2.swift	2	8	25.0%
Sources/Auth/AuthClient.swift	3	15	20.0%

Files with Coverage Reduction	New Missed Lines	%
Sources/Helpers/Logger/SupabaseLogger.swift	10	51.55%
Sources/Realtime/RealtimeChannelV2.swift	44	61.91%

Totals
Change from base Build 18526324821:	-0.9%
Covered Lines:	5884
Relevant Lines:	7666

---

💛 - Coveralls