[BUG] - Outline provider sets all ranges to 0 and ignores user sort order

[multimokia]

Despite being sorted by position, the outline provider always categorizes and only orders inners by position. I think it'd be best to avoid categorizing entirely, as with other languages as well, no explicit categories are made, the icon alone is typically the distinction for type.

Additionally, the outline provider only uses a 0 range for all blocks:

This isn't ideal as it means breadcrumbs have no positional data to invorm the user where they are in the document. It also means the outline is unaware of where the user is in the file.

Functions which can properly block out portions of the file for formal outline providing and potential re-use in the discussed init block handling in #76 (a system to properly handle the starts/ends of blocks is needed) could be built to help.

[duckdoom4]

Please check if this is still an issue as of v2.1.0-pre-release

[multimokia]

Still an issue as items in the outline are classed under callable, class, etc. which makes breadcrumb navigation impossible (as those categories take up a range of 0 starting from the top of the document)

For example, at line 1, column 1:

But for something like this, no breadcrumb info is shown, nor is the outline aware I am editing the function

I would expect outline to show definitions.rpy > MASDummyClass > __call__