Yell Budgeting tool: can set budgets for the wrong month

The synchronizer had a bug where, when it ran at Feb 28, 17:10:00 the date was
converted to GMT (March 1st); this was used to transition the campaigns to use
March as the current month. However, the synchronizer also clears TL/BT/BF
nodes and re-generates them during each run. These nodes were not updated with
the new GMT timing and were in fact not using the command line date at all; thus
the situation occurred that the hierarchy was using February as CurrentMonth
while all of the existing campaigns were using March. The upload tool looks at
all of the BF nodes and checks the file's date against that BF node's date:
here, it was checking March against a CurrentMonth of February and a NextMonth
of March. This would lead it to use NextMonth as the field that needed to be
updated, and it would go through all of the children of that BF and set their
NextMonth targetSpend to the appropriate values... but the campaigns, having
been transitioned properly, had a CurrentMonth of March and a NextMonth of
April, resulting in the issues we saw yesterday.