fix(fyler-nvim): Refactor options for file explorer configuration

[burgr033]

📑 Description

upstream fyler changed their options. It gave a warning message about deprecating the options used in the astrocommunity fork. this pr changes the options to match the structure of fyler.nvim

📖 Additional Information

message

Fyler: Deprecated configuration options detected
============================================================

Deprecated configuration detected: 'default_explorer'
  Configuration structure reorganized under 'views.finder'
  Use 'views.finder.default_explorer' instead
  Update your config: views.finder.default_explorer = true

Deprecated configuration detected: 'indentscope'
  Configuration structure reorganized under 'views.finder'
  Use 'views.finder.indentscope' instead
  Update your config: views.finder.indentscope = {
  marker = "┊"
}

Deprecated configuration detected: 'win'
  Configuration structure reorganized under 'views.finder'
  Use 'views.finder.win' instead
  Update your config: views.finder.win = {
  border = "rounded",
  kind = "replace"
}

============================================================
Please update your configuration to avoid future issues.
See :h Fyler.Config for current options.

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

• Proper usage of opts table rather than setting things up with the config function.

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).