fix(toml): fix empty string handling

[timreichen]

The current toml implementation throws when trying to parse an empty string.
(Probably) all toml npm implementations allow empty strings and return an empty object, so we should probably too.

import toml from "npm:toml";
assertEquals(toml.parse(""), {});

import tomljs from "npm:toml-js";
assertEquals(tomljs.parse(""), {});

import * as s from "npm:smol-toml";
assertEquals(s.parse(""), {});

import * as i from "npm:@iarna/toml";
assertEquals(i.parse(""), {});

import * as c from "npm:confbox";
assertEquals(c.parseTOML(""), {});

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.58%. Comparing base (3a021b2) to head (9226dd5).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6585   +/-   ##
=======================================
  Coverage   94.58%   94.58%           
=======================================
  Files         579      579           
  Lines       43752    43752           
  Branches     6494     6494           
=======================================
+ Hits        41381    41383    +2     
+ Misses       2331     2329    -2     
  Partials       40       40           

☔ 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.

[kt3k]

It looks like empty string should be mapped to {} according to the spec maintainer. toml-lang/toml#607

LGTM

I don't think this is a breaking change. I changed the commit type to 'fix'. (A breaking change is an intentional design change, which breaks the users' code. The existing behavior is unintentional bug.)