Expose PutHumptyTogetherAgain method in LfMergeBridge

[rmunn]

The LexBox project wants to be able to generate .fwdata files on the fly, which will enable various features such as being able to view recent changes to a project in a nicer form than Mercurial diffs. In order to make this work, we need to expose the PutHumptyTogetherAgain method as a public method.

This PR seems the simplest way to do it, enabling access to that API from LfMergeBridge without changing the access granted to any other projects. That way we minimize the risk to FLEx and WeSay, as the code they use is not touched at all.

---

This change is 

[jasonleenaylor]

Reviewable status: 0 of 1 files reviewed, all discussions resolved

---

src/LfMergeBridge/LfMergeBridge.cs line 75 at r1 (raw file):

		}

		public static void PutHumptyTogetherAgain(IProgress progress, bool writeVerbose, string mainFilePathname)

This is an opportunity, should you want one, to adjust the name.

Code quote:

PutHumptyTogetherAgain

[rmunn]

Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @jasonleenaylor)

---

src/LfMergeBridge/LfMergeBridge.cs line 75 at r1 (raw file):

Previously, jasonleenaylor (Jason Naylor) wrote…

This is an opportunity, should you want one, to adjust the name.

Good point. I've pushed a new commit to use more boring, but easier to understand, names. And while I'm at it, I've decided to expose the reverse operation too; I have no need for it yet in the code I'm about to write in LexBox, but could definitely see a need for this in future features.

[rmunn]

I'm assuming Jason would have mentioned any objections if he had them; since this affects nothing except the code that interfaces with LfMerge, I'm going to go ahead and merge it now.