Implement log tagging for SDK logs

[gasperzgonec]

Description

This PR changes how the SDK internal logs are printed. As it currently stands, the SDK logs are all prefixed with SDK: .

Connected Issues

• #ISS-202822

Checklist

• Tests added/updated and ran with npm run test OR no tests needed.
• Ran backwards compatibility tests with npm run test:backwards-compatibility.

• no-docs
• Tested airdrop-template linked to this PR.

[radovanjorgic]

TBH I don't understand this whole complexity behind. So, what we want achieve is just prefixing SDK logs with [SDK] or sth like that, and possibly user logs with [USER]. Most likely I don't understand security issues here, but seems a bit like an overkill to me and sth that can overcomplicate our lifes. Let's discuss this on call.

[radovanjorgic]

I added few suggestions, will probably add more comments in second review. However, since logger overrides console, can we use console.log/error/warn... at all other places, let's have clear distinction here?

Also, let's ask @navneel99 for quick review after tomorrow's meeting.

[gasperzgonec]

The code has been rewritten to support new linting addition.
I've kept the Token approach, but added the factory pattern for accessing internal or user logger.

Functions inside of logger.ts are private and aren't exported, so the access to the function is prevented. If user decided to import the source from the repo and wanted to spin up a new instance of Logger, the token would be incorrect and the creation would fail.

With the new changes:

• tests pass
• it is backward compatible
• it's been linted
• tested with airdrop-template

[radovanjorgic]

Added few comments, looks much better now.

[radovanjorgic]

LG, please test in both local mode and on lambda.