refactor: standardize fb_action user IO

[jamestrew]

Using vim.notify for output messages (log level = WARN for areas indicating missteps by users), vim.ui.input for inputs.

All messages prefixed by [telescope] to be clear about the origins of the message.

Checks off an item from #3

[kkharji]

awesome refactor

[kkharji]

Makes sense

[fdschmidt93]

Sorry, a bit too lazy right now as I've had worked on tons on the file browser in the weeks before. I'll try to get to have a first brief crack at this either tomorrow or Sunday :)

E: And of course thanks for your PR :)

[jamestrew]

Throwing this PR into draft mode to do some clean up and find a solution to #87, #91

[jamestrew]

closes #91

I've spent some more time looking for solutions for #87 but I'm able to find something that works consistently.
So far, I'm using vim.api.nvim_command("norm :esc<CR>") and it works for all actions expect remove (due to things being printed prior to the [y/N] input getter). Also for get_valid_path if the user completely deletes the default input, it will also print the Operation aborted msg on the same line as the input prompt. There's a lot of strange behaviors I'm running into between vim.ui.input and print/vim.notify... pretty frustrating.

If anybody has any suggestions, that'll be great.

[fdschmidt93]

I've now looked a bit more at this as I'll eventually will take this over. Couple of notes:

• vim.ui.input is async for most users that eg user dressing.nvim or telescope-ui-select; hence, we cannot rely returning anything from vim.ui.input
• vim.cmd [[redraw!]] is probably the most reliant way to avoid hit-enter prompt

I'll try to work incrementally and push the PR maybe in a week or two.

Thanks again anyways :)