feat: handle possible issue with initial load when lazy loading

## Details

Issue: #309

Depending on how the plugin manager implements lazy loading, this plugin can
miss the initial buffer that triggered it to load.

This is because we setup a `FileType` autocommand to check which buffers
we should attach to. If the user configures this plugin to load based on
a filetype that event will not be processed by the autocommand (since it
has not been created yet). Instead everything will be setup but the
current buffer will end up ignored.

I'm unsure why this is not an issue with `lazy.nvim`, maybe it executes
autocommands after the initial load. This would make sense, but I have
not verified it.

To get around this attempt to attach to the current buffer at the start,
similar to the command based lazy loading edge case.

Author: MeanderingProgrammer

lua/render-markdown/health.lua

@@ -5,7 +5,7 @@ local state = require('render-markdown.state')
 local M = {}
 
 ---@private
-M.version = '7.8.11'
+M.version = '7.8.12'
 
 function M.check()
     M.start('version')

lua/render-markdown/manager.lua

@@ -14,6 +14,8 @@ M.group = vim.api.nvim_create_augroup('RenderMarkdown', { clear = true })
 
 ---Should only be called from plugin directory
 function M.setup()
+    -- Lazy Loading: ignores current buffer as FileType event already executed
+    M.attach(util.current('buf'))
     -- Attempt to attach to all buffers, cannot use pattern to support plugin directory
     vim.api.nvim_create_autocmd('FileType', {
         group = M.group,
@@ -40,7 +42,7 @@ end
 
 ---@param enabled boolean
 function M.set_all(enabled)
-    -- Attempt to attach current buffer in case this is from a lazy load
+    -- Lazy Loading: all previously opened buffers have been ignored
     M.attach(util.current('buf'))
     state.enabled = enabled
     for _, buf in ipairs(buffers) do