fix(rome_service): correctly send file source to workspace

[ematipico]

Summary

Closes #4458

The previous PR was send the default SourceType, which wasn't the correct way.

This PR fixes the issue by doing the following:

• renaming "source type" to "file source";
• creating a tiny trait called FileSource, which will be used to share behaviour for those file sources that need to be sent across thread boundaries;
• creating a new type called AnyFileSource, a language-agnostic data structure that will be used when using the Workspace. This type has a method called try_from, which will attempt to recreate the file source based on the path of the file

I renamed SouceType to JsFileSource.

Test Plan

Current tests should pass. I created a new test case to fix the issue

Changelog

• The PR requires a changelog line

(I will create changelog line in next-release branch, to avoid too many conflicts)

Documentation

• The PR requires documentation
• I will create a new PR to update the documentation

[netlify]

✅ Deploy Preview for docs-rometools canceled.

Name	Link
🔨 Latest commit	49bd68f
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rometools/deploys/645e7bdcdd09d6000810ec5f

[github-actions]

Parser conformance results on ubuntu-latest

js/262

Test result	main count	This PR count	Difference
Total	48863	48863	0
Passed	47796	47796	0
Failed	1067	1067	0
Panics	0	0	0
Coverage	97.82%	97.82%	0.00%

jsx/babel

Test result	main count	This PR count	Difference
Total	40	40	0
Passed	37	37	0
Failed	3	3	0
Panics	0	0	0
Coverage	92.50%	92.50%	0.00%

symbols/microsoft

Test result	main count	This PR count	Difference
Total	6212	6212	0
Passed	1763	1763	0
Failed	4449	4449	0
Panics	0	0	0
Coverage	28.38%	28.38%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	639	639	0
Passed	573	573	0
Failed	66	66	0
Panics	0	0	0
Coverage	89.67%	89.67%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	17224	17224	0
Passed	13127	13127	0
Failed	4097	4097	0
Panics	0	0	0
Coverage	76.21%	76.21%	0.00%

[ematipico]

Turns out we can't use a unwrap_cast, but we have to gracefully handle the error. Via LSP, we can get documents that don't have extensions, and those should not throw a panic.