Update sizes expectation for mini_installer.exe

Update xp-release/sizes/mini_installer.exe expectations.

A 2MB+ regression was introduced but a cause cannot be identified.

https://chromeperf.appspot.com/report?masters=Chromium&bots=chromium-rel-xp&tests=sizes%2Fmini_installer.exe&checked=mini_installer.exe&rev=294272

BUG=413191
NOTRY=true
TBR=weitaosu,engedy

Committed: https://crrev.com/ed0021074af680d11d16f6eefac52f05b43d23f2
Cr-Commit-Position: refs/heads/master@{#294512}

[Zeeshan Qureshi, 2014-09-11 22:00:45]

zeeshanq@chromium.org changed reviewers:
+ engedy@chromium.org, weitaosu@chromium.org

[Zeeshan Qureshi, 2014-09-11 22:00:45]

Updating sizes to get the bot green, will track regression in bug.

[Zeeshan Qureshi, 2014-09-11 22:02:08]

The CQ bit was checked by zeeshanq@chromium.org

[Zeeshan Qureshi, 2014-09-11 22:02:28]

The CQ bit was unchecked by zeeshanq@chromium.org

[weitao, 2014-09-11 22:05:54]

On 2014/09/11 22:00:45, Zeeshan Qureshi wrote:
> Updating sizes to get the bot green, will track regression in bug.

LGTM. What is sha1 and how did you obtain it?

[Zeeshan Qureshi, 2014-09-11 22:07:50]

On 2014/09/11 22:05:54, weitaosu wrote:
> On 2014/09/11 22:00:45, Zeeshan Qureshi wrote:
> > Updating sizes to get the bot green, will track regression in bug.
> 
> LGTM. What is sha1 and how did you obtain it?

You have to update reva/b and the make_expectations.py script updates the
numbers.

[Zeeshan Qureshi, 2014-09-11 22:07:57]

The CQ bit was checked by zeeshanq@chromium.org

[commit-bot: I haz the power, 2014-09-11 22:24:19]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/569453002/1

[Zeeshan Qureshi, 2014-09-11 23:56:49]

The CQ bit was unchecked by zeeshanq@chromium.org

[Zeeshan Qureshi, 2014-09-12 00:05:31]

The CQ bit was checked by zeeshanq@chromium.org

[commit-bot: I haz the power, 2014-09-12 00:14:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/569453002/1

[commit-bot: I haz the power, 2014-09-12 00:56:55]

Committed patchset #1 (id:1) as a693ce67bcd7e05c5ef168ab0875dd940520e273

[commit-bot: I haz the power, 2014-09-12 00:59:26]

Patchset 1 (id:??) landed as
https://crrev.com/ed0021074af680d11d16f6eefac52f05b43d23f2
Cr-Commit-Position: refs/heads/master@{#294512}

[engedy, 2014-09-12 09:58:48]

On 2014/09/12 00:59:26, I haz the power (commit-bot) wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/ed0021074af680d11d16f6eefac52f05b43d23f2
> Cr-Commit-Position: refs/heads/master@{#294512}

LGTM, although I consider this more of a temporary fix. We probably do not want
to allow our installer increase in size by 2 megs overnight, therefore
*somebody* with more background should investigate more.