Introduce get_kedro_project_json_data function for VSCode integration

[jitu5]

Description

Resolves #2021

To get current Kedro project JSON data required by Kedro-Viz React component when running inside VSCode, We introduce get_kedro_project_json_data function in responses.py which returns current Kedro project JSON data.

Development notes

• This function will call from Kedro VSCode extension
• Before calling get_kedro_project_json_data function, load_and_populate_data will be called

Checklist

• Read the contributing guidelines
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added new entries to the RELEASE.md file
• Added tests to cover my changes

[astrojuanlu]

And also, would it make sense longer term to extract that functionality to a self-contained package? Thinking for example of the defunct https://github.com/AlpAribal/kedro-inspect/

[noklam]

And also, would it make sense longer term to extract that functionality to a self-contained package? Thinking for example of the defunct https://github.com/AlpAribal/kedro-inspect/

This definitely make sense, but I would like to see this happen at a core level where kedro has a better way of serialise/deserialise a Pipeline. Otherwise the current JSON data structure is very much coupled to kedro-viz, and I don't see much benefit of making it a separate package itself. Maybe just making kedro-viz a leaner package would help. similiar to the kedro-core discussion, maybe kedro-viz[core] or kedro-viz[standard].

https://nbviewer.org/github/noklam/kedro-viz-lite/blob/main/nbs/10_demo.ipynb, regardless of a separate package /refactoring, I would like to see this can be done in a notebook, where I can easily convert an existing Pipeline object. The notebook has shown that Pipeline is the only thing that is needed, we don't really need a full Kedro project to generate the flowchart JSON.

[rashidakanchwala]

LGTM. thanks!