Switch from METADATA to registrator

[kescobo]

With the new package registration system, REQUIRE is out and Project.toml is in.

This is an annoying but necessary task, so I thought I'd just do it. I used this script, and added a version (0.14.0, since I figured this warranted a major version bump).

[nalimilan]

0.14.0, since I figured this warranted a major version bump

Does it? I don't think so, as nothing changes at all for users (the registries already generated the Project.tool file automatically under the hood).

[alyst]

Before the new release, I would like to merge #168, which is a (small) API change warranting a major version bump.
BTW, @nalimilan could you please take a look at #168?

[kescobo]

Fine by me either way. Let me know if you want me to change it or leave it alone :-)

[alyst]

I think the consensus now is that the next release will be 0.13.2.
@kescobo Could you please commit the suggested change and add version, so that I can merge the PR?

[kescobo]

@alyst All set!

[alyst]

@kescobo Thanks! Actually, I've never used Registrator before :) Should I add the comment @JuliaRegistrator register + release notes and then merge?

[JuliaRegistrator]

Pull request comments will not trigger Registrator as it is disabled. Please trying using a commit or issue comment.

[kescobo]

@alyst Evidently not? 😆

I've only used BioJulia's registrator, but I did it in an issue after the PR was merged. Seems like it makes the most sense to do in in the PR once it's merged but ¯_(ツ)_/¯

[alyst]

Also I should be careful calling the registrator by name, since it doesn't understand the quotes. :)
I'll try commenting the head commit after merging the PR.