Profile date fields are incorrectly rendered by views field handler

Summary

In a view showing a profile date field set to the first day of any month/year, the month will be rendered as the wrong month depending on the site's configured timezone.

Steps to repeat

1. Create a profile date field
2. Set the new date field's value to [any month] 1, [any year] (i.e. the first day of any month/year combination)
3. Create a view that displays profile date field
4. If your site's timezone in in America (and other negative GMT offsets) you will probably see the bug occur

Resolution

Using gmdate instead of date resolves the issue since timezone values are ignored in gmdate (preferred behavior)