Print migration guide on version SDK/Starport version mismatch

[fadeev]

Output the migration file from docs.

[ilgooz]

@Pantani any thoughts about the impl details on this?

This is what I have in my mind:

We create a new func under a pkg something like: pkg/offlinepage.Markdown(mdPath string) (htmlPath string, err error)

When we need to navigate users to the migration guideline, we basically call Markdown() with the path we create for docs/migration/VERSION.md through localfs.SaveTemp() pkg. Please also see the docs pkg.

Then, Markdown() returns the path for resulting html file for the migration guideline, we can either render the html in the Go side, or move contents of the MD into html and render in the browser with an embedded JS lib. After html created, we print its path to the user file:///private/tmp/starport-migration-VERSION.html. I think it's nice to create a human readable link like this for convenience. The file can be saved in user's tmp dir.

If needed we can also use anchors # to navigate to a specific section. file:///private/tmp/starport-migration-v0.18.0.html#ibc-upgrade.

[Pantani]

I like the approach. Is it similar I thought.... we will keep all these migration markdown files in the same folder? I can create a embed.FS for the entire folder and convert everything to a local HTML folder. The user can access all migration, in a case that needs to up more than one version, he needs to access the other migration files.

[ilgooz]

Instead of adding a new embed line, you can basically use https://pkg.go.dev/io/fs#Sub to access migration dir from docs.Docs

[Pantani]

I created the logic to create the HTML files based on the migrations markdown, but I'm not sure the best place to verify the version mismatch and call the method.