Parse performance optimizations

[wieslawsoltes]

Optimizes performance and memory usage for Parse operations.

This PR has been split and summary moved to tracking issue #802

Split status:

• Source/DataTypes/SvgNumberCollection.cs Performance optimizations for SvgNumberCollectionConverter parser #807
• Source/DataTypes/SvgPointCollection.cs Performance optimization for SvgPointCollectionConverter parser #808
• Source/DataTypes/SvgUnitCollection.cs Performance optimization for SvgUnitConverter / SvgUnitCollectionConverter #805
• Source/DataTypes/SvgUnitConverter.cs Performance optimization for SvgUnitConverter / SvgUnitCollectionConverter #805
• Source/Helpers/FloatParser.cs Adds common string parser class with parse helper methods #801
• Source/Helpers/StringSplitEnumerator.cs Adds common string parser class with parse helper methods #801
• Source/Painting/SvgColourConverter.cs Performance optimizations for SvgColourConverter parser #806
• Source/Paths/CoordinateParser.cs Use StringParser class in CoordinateParser #804
• Source/Paths/SvgPathBuilder.cs Refactor SvgPathBuilder to have Parse that accepts ReadOnlySpan<char> #810
• Source/Transforms/SvgTransformConverter.cs Refactor SvgTransformConverter to have Parse method and use StringParser #809
• Tests/Svg.Benchmark/CoordinateParserBenchmarks.cs Use StringParser class in CoordinateParser #804
• Tests/Svg.Benchmark/Program.cs Correct Svg.Benchmark namespaces and cleanup csproj #803
• Tests/Svg.Benchmark/README.md Correct Svg.Benchmark namespaces and cleanup csproj #803
• Tests/Svg.Benchmark/Svg.Benchmark.csproj Correct Svg.Benchmark namespaces and cleanup csproj #803
• Tests/Svg.Benchmark/SvgColourConverterBenchmarks.cs Performance optimizations for SvgColourConverter parser #806
• Tests/Svg.Benchmark/SvgDocumentBenchmarks.cs Correct Svg.Benchmark namespaces and cleanup csproj #803
• Tests/Svg.Benchmark/SvgNumberCollectionConverterBenchmarks.cs Performance optimizations for SvgNumberCollectionConverter parser #807
• Tests/Svg.Benchmark/SvgPathBuilderBenchmarks.cs Refactor SvgPathBuilder to have Parse that accepts ReadOnlySpan<char> #810
• Tests/Svg.Benchmark/SvgPointCollectionConverterBenchmarks.cs Performance optimization for SvgPointCollectionConverter parser #808
• Tests/Svg.Benchmark/SvgTransformConverter.cs (only rename) Correct Svg.Benchmark namespaces and cleanup csproj #803
• Tests/Svg.Benchmark/SvgTransformConverterBenchmarks.cs Refactor SvgTransformConverter to have Parse method and use StringParser #809
• Tests/Svg.Benchmark/SvgUnitCollectionConverterBenchmarks.cs Performance optimization for SvgUnitConverter / SvgUnitCollectionConverter #805
• Tests/Svg.Benchmark/SvgUnitConverterBenchmarks.cs Performance optimization for SvgUnitConverter / SvgUnitCollectionConverter #805
• Tests/Svg.UnitTests/MarkerEndTest.cs Refactor SvgPathBuilder to have Parse that accepts ReadOnlySpan<char> #810
• Tests/Svg.UnitTests/PerformanceTest.cs

[mrbean-bremen]

@wieslawsoltes - just a suggestion: I would propose to split this PR into several PRs, e.g. get the current one working, let it review (I'm hoping for @inforithmics here) and merge it and go for the next bunch. This way reviewing will be easier, you have stable versions you can rely on, and there are less possible conflict with other changes.

[wieslawsoltes]

@wieslawsoltes - just a suggestion: I would propose to split this PR into several PRs, e.g. get the current one working, let it review (I'm hoping for @inforithmics here) and merge it and go for the next bunch. This way reviewing will be easier, you have stable versions you can rely on, and there are less possible conflict with other changes.

That is good idea, I will try to finish the current work and continue the rest in another PRs.

[wieslawsoltes]

Closing this as changes have been split into smaller PRs