`convertPathData` introduces floating point precision errors at high precision settings (CLI)

[Goodwine]

Describe the bug

I encountered an issue where convertPathData produces significantly larger output because a number gets "rounded" to a much longer floating-point form (e.g., ending in ...9999996). This seems to be a floating-point precision bug that occurs specifically when using the CLI.

To Reproduce
Steps to reproduce the behavior:

1. Create a file named test.svg with the following content:

   <svg><path d="M13.017 2.13-4.61-1.265"/></svg>

2. Create a config file named config.cjs:

   module.exports = {
     plugins: ['convertPathData'],
   };

3. Run the SVGO CLI command with precision set to 16:

   npx svgo test.svg --config config.cjs --input test.svg --output result.svg -p 16

4. Observe the output in result.svg.

Expected behavior

The output numbers should remain concise and correct, rather than expanding into long floating-point representations that actually increase the file size.

Actual Output

<svg><path d="m13.017 2.13-17.627-3.3949999999999996"/></svg>

Desktop (please complete the following information):

• SVGO Version 4.0.0
• Node.js Version 20.19.1
• npm version 10.8.2
• OS: Ubuntu 20.04.0 LTS

Additional context

• I can only replicate this with the CLI tool. I could not replicate it when using SVGO as an NPM library. I was able to replicate using SVGO as an NPM library, see comment below

• In this minimal reproduction case above, setting -p 15 resolves the issue changes the behavior to a more acceptable output, but is still longer than if it didn't change anything. See comment about it below.

[Goodwine]

Ah, actually, I was able to repro using SVGO as a library with this setting:

{"name":"convertPathData","params":{"floatPrecision":16}},

I was trying optimize(input,{plugins:["convertPathData"], precision: 16}) before, and that didn't repro, but setting the precision value directly on the plugin parameters did repro.

[Goodwine]

Another realization

• When using -p 16, I get <svg><path d="m13.017 2.13-17.627-3.3949999999999996"/></svg>
• When using -p 15, I get <svg><path d="m13.017 2.13-17.627-3.395"/></svg>
• when using -p 14, I get <svg><path d="M13.017 2.13-4.61-1.265"/></svg> (same as input)

[GreLI]

Well, I would not recommend high precision settings generally. Just because of floating point issues. More than 9 is actually overkill (due to how multiplication works). More than 15 probably is not practical to any approach.