Make pipeline discovery more flexible

[noklam]

Problem

The plugin need to understand what is "pipeline" in order to support "Clicking on a symbol and navigate to catalog.yml or parameters.yml".

The current situation is, the extension assumes project follows a standard modular pipeline structure and re-implement logic similiar to find_pipelines in kedro:

• pipelines
  • sub_pipleline
  • pipeline.py

This mean that a project that deviate from this convention will not function properly, such as:

- pipelines
  - sub_pipeline
    - pipeline_data_processing.py

Possible solution:

• Expand the pipeline discovery logic to support *pipeline*.py
• Allow user to customise pipeline discovery