formats.h:define FMT_MAIN_VERSION earlier than before

The definition has been moved more to the top of formats.h.
to allow using #if FMT_MAIN_VERSION > 11 ... #endif
for the definition of fmt_main components inside formats.h,
and not just inside format definitions.
You can also use #if FMT_MAIN_VERSION > 11 so thatjohn's
logic, e.g. availability of certain options, can be altered
depending on format version.
New options could be suppressed if the older format definition
does not include the components that are required for the new
optiion to work.
When developing new features, this allows to move most of
the plugin formats to unused, adjust the few remaining formats,
implement the core functionality, revert FMT_MAIN_VERSION to the
older version, restore all the formats previously moved to unused...

It would be good if this trivial change could be applied to core
as well.
define a FLG_COST for new option --cost

before we run out of available flags (again).
I intend to come up with a syntax that alows to specify
min/max values or ranges for multiple tunable costs with
a single option (and thus, a single flag).
Since adjusting all existing formats to the new format definition
will take time, I want to avoid spending all this effort without
any assurance that we ran out of flags once I am ready to create
a pull request.
xsha512 format will not crack OS X 10.8 or higher (see 6947648242ca51260945d2dab8e1af129362fbc2).
Merge pull request #555 from claudioandre/bleeding-jumbo

xsha512 format will not crack OS X 10.8 or higher (see 6947648).
Merge pull request #554 from frank-dittrich/bleeding-jumbo

formats.h:define FMT_MAIN_VERSION earlier than before
Merge branch 'bleeding-jumbo' into memdbg

* bleeding-jumbo:
  xsha512 format will not crack OS X 10.8 or higher (see 6947648242ca51260945d2dab8e1af129362fbc2).
  define a FLG_COST for new option --cost
  formats.h:define FMT_MAIN_VERSION earlier than before