feat(fyler-nvim): update fyler.nvim config to replace neotree.nvim

[Jac-Zac]

📑 Description

This PR replaces neo-tree with fyler.nvim as the default file explorer and enhances its usability.

Key changes:

• Disabled neo-tree to prevent conflicts.
• Set fyler as the default explorer (default_explorer = true).
• Open in a floating window with <Leader>e.

These updates make fyler.nvim fully integrate as the main file explorer with improved UX.

📖 Additional Information

• Fully integrated with astrocore mappings.
• Floating mode avoids blocking the main buffer.
• Visual and interaction enhancements for smoother navigation.

Note: Breaking Change

The keybinding used is different but is in line with other plugins such as the mini-files plugin and the default neo-tree moreover the default mode is floating.

My config:

Though something like this could be used instead:

[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).

[Uzaaft]

Can you update the original PR desc @Jac-Zac. Its outdated at this point.

[Jac-Zac]

Can you update the original PR desc @Jac-Zac. Its outdated at this point.

Is this small edit I applied to the PR description good ?

[Uzaaft]

looks good, i just wanted the pr message to reflect the content when I reviewed 😅. I'll be doing a pass in 12h, but this looks good so far from my quick pass!

stale