Improve performance of commented string

[adellibovi]

Short description 📝

This PR improves the performance of commented string.

Solution 📦

Most of the case we do not need to escape, having an early exit saves a lot of copies and allocation, in my case I got the time spent on validString from 9s to 1.6s

[codecov-commenter]

Codecov Report

Merging #635 (f0f5905) into main (e4f1ee6) will decrease coverage by 0.31%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #635      +/-   ##
==========================================
- Coverage   84.34%   84.03%   -0.32%     
==========================================
  Files         154      154              
  Lines        8758     8774      +16     
==========================================
- Hits         7387     7373      -14     
- Misses       1371     1401      +30     

Impacted Files	Coverage Δ
Sources/XcodeProj/Utils/CommentedString.swift	91.48% <100.00%> (-1.67%)	⬇️
Sources/XcodeProj/Project/XcodeProj.swift	38.93% <0.00%> (-6.02%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e4f1ee6...f0f5905. Read the comment docs.

[fortmarek]

🚀 Just to double-check - have you made sure there are tests in place that would have caught possible regression?

[adellibovi]

🚀 Just to double-check - have you made sure there are tests in place that would have caught possible regression?

Yep, there were already a good collection of cases under CommentedStringTests ☺️
Also tested the generation with a Tuist integration