Experimental API for malysis integration

[OmkarPh]

Primarily, I've introduced another core.File implementation - readerFile (can be renamed to "artifactFile" / "standaloneFile" / any suggestions ?)
This allows using ArtifactFile to be used with already available plugin APIs

This can be used in malysis in place of static.go#L201 like -

lang, _ := lang.ResolveLanguageFromPath(af.Name)
artifactParser, err := parser.NewParser(lang)
var readerFile core.File = fs.NewFileFromReader(af.Reader, af.Name, false)
parseTree, _ := artifactParser.Parse(ctx, readerFile)

var buf []byte
stripcommentsPlugin := stripcomments.NewStripCommentsPlugin(func(ctx context.Context, scpd *stripcomments.StripCommentsPluginData) error {
  scpd.Reader.Read(buf)
  return nil
})

if slices.Contains(stripcommentsPlugin.SupportedLanguages(), lang.Meta().Code) {
  stripcommentsPlugin.AnalyzeTree(ctx, parseTree)
} else {
  buf, err = io.ReadAll(io.LimitReader(af.Reader, readLimit))
}

Maybe, we can also have a util function for reusability, created at malysis level, which accepts an artifactFile and returns a io.Reader (reader from StripCommentsPluginData or the default one in case of unsupported lang)

[abhisek]

Suggested change

	func NewReaderFile(reader io.Reader, path string, isImport bool) *readerFile {
	func NewFileFromReader(reader io.Reader, path string, isImport bool) *readerFile {

[abhisek]

Add a documentation for this function since it is exported.

[abhisek]

Add a documentation for this function since it is exported.

[abhisek]

Suggested change

	func ResolveLanguage(filePath string) (core.Language, error) {
	func ResolveLanguageFromPath(filePath string) (core.Language, error) {

Since this is an exported function and package global (i.e. not within a struct receiver), I think we should name it as explicitly as possible.

[abhisek]

@OmkarPh The Code framework related changes look good to me. I think they are generic enough and can be utilized for various use-cases where we want to parse & analyse a single file and not an entire directory / filesystem. Let us go ahead with this change in Code.

[abhisek]

Please add a test for this.

[OmkarPh]

updated naming and docs

[abhisek]

@OmkarPh Is this ready for review? I see this is still in draft status