* Update Persian translation for 1.6.3

* Change Translation Status for Persian

Since Obsidian Persian translate is not complete, i've changed it to 

* Update fa.json

Edits and new translations

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

Edits and new translations

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

* Update fa.json

New templates for kh, lt, nn, uz

Full Revision of Persian/Farsi Translation after about 5 months. Mostly translated but Ready to be used in Obsidian. (#604)

* First Commit

* 2nd

* 3rd

* 4th

* 5th

* ۶فا

* 7th

* 8th

* 9th

* 10th

* 11th

* 12th

* 13th

*  Added Farsi Termbase + More strings translated

*  Changed fa.termbase name to fa.guidelines + Added new terms to fa.guidelines + More Strings added & Translated

*  Some improvements

*  Additions & Improvements

*  Additions & Fixes

* More!

* Added & Fixed

* ...

*  Crushed some of those stubborn strings

*  Some sections are now completely translated!

* + Some terms changed, more strings translated

* Many sections are now complete :D + Made Guideline file better.

* Command Palette Translations + More nouanced trans. for the Term "Toggle"

* ...

* fixed typos

* 1st edition is Ready

* ...

* Alphabetically sorted the terms

*  Translated Most of the String except some strings in Core Plugins.

*  Removed the old translation file +  Updated Guidelines

*  Translated some lines

* Update fa.json

* Update fa.json

* Translated more strings. Changed "Obsidian"'s transliteration.

* Update fa.json

* Brought back the previously translated strings.

Some of the previously translated strings were somehow lost in the process of doing the overhauled translation (as you pointed out), they are now back (except for one string that I've intentionally decided not to translate).

* Changed the status for Farsi to 

I believe it is pretty much ready to be used in the app.

The publish action opens an intermediate modal. The `...` will signal to users that the action isn't immediate and might make it more welcoming.

I have got a couple of questions and bug reports about this.
Some people expect this setting to apply to notes opened in the same pane, whereas this settings is only about new panes.

Made description of markdown autopair setting consistent with its behavior.