Update p5-DateTime-Locale to 1.01.

Remove duplicate depends, add test dependencies.

1.01     2015-11-07

- Prevent CPAN from indexing the tools directory, which is just for the
  author's use.

1.00     2015-11-07

* All of these changes were originally released in previous trial releases,
  but I'm repeating them here for clarity.

[ENHANCEMENTS]

- This release uses the locale data from CLDR version 28. The last major
  update of the locale data used CLDR 1.7.1, released in 2009, so this is a
  big change. Many things have changed in terms of locale data.

- Some locales are no longer available because they are not in the CLDR data.

- The CLDR data no longer includes default date and time format lengths. This
  is now "medium" for every locale, simply to provide some level of backwards
  compatibility.

- Loading DateTime::Locale itself is now quite a bit faster. The whole locale
  registration system has been removed entirely, except for custom
  locales. This fixes RT #78794. Requested by Michael Conrad.

- A long-standing issue with the Austrian locale not using the Austrian name
  for January has been fixed. RT #52337. Reported by Thomas Klausner.

[BACKWARDS INCOMPATIBILITIES]

- This is a big new release, and includes a number of backwards-incompatible
  changes. However, most users should be unaffected by this change. If you
  only use this module via DateTime.pm, you are unlikely to notice any changes
  other than changes to the locale data.

- The old API deprecated since 0.40 has been removed (almost) entirely.

- We now refer to things as "code" in the docs and method names where we used
  to call them ids. This includes locale, language, script, territory, and
  variant codes. This is more in line with the various ISO standards and the
  CLDR packages.

- All the $locale->*_id methods (including $locale->id) are deprecated. Use
  the relevant $locale->*_code method instead.

- The canonical form of the locale codes now uses dashes (-) instead of
  underscores (_). Loading a locale with an underscore in the name
  (e.g. en_US) still works.

- The way that locale data is packaged has changed quite a bit. We no longer
  package each locale in its own class. Instead, all locale data is in a
  single module (mostly in a __DATA__ section) and loaded into memory as
  needed. If you have any code that checks $locale->isa, that code may
  break.

- Locales are no longer subclasses of DateTime::Locale::Base. This module is
  still included in the distribution in case someone has a custom locale that
  inherits from this module. However, this module will go away in a future
  release.
z
- The "ii-*" aliases for the "he-*" locales have been removed.

- The "no-*" aliases for the "nn-*" locales have been removed.

- The value of $locale->code no longer reflects the value passed to
  DateTime::Locale->load. This only affects aliases and non-canonical forms of
  the code. For example, if you load "en_US" then $locale->code will return
  "en-US". If you load "C" or "POSIX" the returned code will be "en-US-POSIX".

- All of the documentation related to creating aliases and registering custom
  locales has been removed. All of these methods still work, but I don't think
  this system got much use, so I don't want to emphasize it in the docs. (But
  let me know if you are using this and want to see these docs restored).

0.96     2015-10-04 (TRIAL RELEASE)

- Locale data with characters in the 0x80-0xFF range was not marked as UTF-8
  by Perl. This could cause all sorts of weirdness and was generally bad.

0.95     2015-09-30 (TRIAL RELEASE)

- Added .pod files for each locale that document the data for that locale.

0.94     2015-09-30 (TRIAL RELEASE)

- Restored the datetime_format method to individual locale objects for
  backwards compatibility.

0.93     2015-09-28 (TRIAL RELEASE)

- Really release a trial release this time. I'm not kidding. See 0.90 for the
  interesting changes.


(wiz)