feat: add keymaps for floating window

[Tronikelis]

closes #172

I am up for discussion on how to call these settings and where to put them

fyi I tested the changes locally

Another approach would be to architecture settings like this:

win_mappings = {
	tags = {},
	scopes = {},
	loaded_scopes = {},
}

Not really sure which one's betteer

[edwardbaeg]

Very excited about this new feature!

[Tronikelis]

@cbochs friendly bump :))

[cbochs]

@Tronikelis apologies for the late reply. I was away on vacation for the past several weeks. Will take a look here soon 🙂

[cbochs]

This is a good start to making mappings more customizable! Left a couple comments.

One note: I think (at least for now) I would prefer that the go_up_scope be fixed. It doesn't have a good common action between the different windows. For example, Tags -> Scopes, Scopes -> Loaded (containers), Loaded (containers) -> Scopes.

It almost feels like there should be separate maps for each:

tag_mappings = { go_to_scopes = "-" }
scope_mappings = { go_to_loaded = "-" }
loaded_mappings = { go_to_scopes = "-" }

But needs a bit more thought, I think. In addition, I don't really like the name loaded. It obscures what is this window is really for: Grapple containers. Something I would like to resolve in the near future would be to rename this from "loaded" to "containers".

[cbochs]

Some action name change suggestions:

• unload_scope -> unload and put in the loaded_mappings table
• reset_scope -> reset and put in the loaded_mappings table
• change_scope -> change and put in the scope_mappings table
• select_horizontal -> select_split and put in the tag_mappings table
• select_vertical -> select_vsplit and put in the tag_mappings table

[Tronikelis]

thanks for the insights, I'll change it

[Tronikelis]

did you list all the renames here? Or is something left

[Tronikelis]

@cbochs I've changed the names based on your comments, please check if I got everything right

[Tronikelis]

@cbochs could we get this merged?