feat(api): use logfmt as logging format

[PabloCastellano]

Checklist

• My change requires a documentation update, and I have done it.
• I have added tests to cover my changes.
• I have filled out the description and linked the related issues.

Description

Change logging format to logfmt

Motivation and Context (Optional)

This format is supported with Loki by default and is much cleaner than JSON

Related Issue (Optional)

Screenshots (if appropriate):

[changeset-bot]

⚠️ No Changeset found

Latest commit: ab488f7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

❌ Patch coverage is 12.19512% with 36 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.05%. Comparing base (7817ea7) to head (ab488f7).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/logger/src/index.ts	12.19%	36 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #909      +/-   ##
==========================================
- Coverage   86.12%   86.05%   -0.08%     
==========================================
  Files         181      181              
  Lines       13963    13973      +10     
  Branches     1292     1293       +1     
==========================================
- Hits        12026    12024       -2     
- Misses       1937     1949      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

📦 Next.js Bundle Analysis for @blobscan/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌