Extend textDocument/documentSymbol to cover more symbols

[anderseknert]

With #668 we got basic support for textDocument/documentSymbol, which means we currently iterate over all the "public", or top-level identifiers, like packages, rules, functions. This seems to cover the most important aspect of this, which is to quickly get an overview of a package and to be able to navigate around between the rules/functions. Regal doesn't settle for basic though, so we should look into extending our coverage here, and include things like values and symbols inside of rule bodies.

I think objects and arrays in particular would be helpful, as it would be helpful to see where in deeply nested constructs the cursor is. But I'm sure we'll find other useful aspects of this as we make progress.

[anderseknert]

One thing to note is that the implementation of workspace/symbol fetches document symbols from each document. We probably don't want things like values to be seen in the workspace symbol search, so filtering out anything but the top level attributes from there is probably a good idea.

[anderseknert]

Having thought more about this, I think the symbols we'll want to cover are:

• objects
• arrays
• comprehensions

in other words, anything that increases the nesting level. When we have that, I think we can consider this issue as resolved.