fix: extractnumber_xx API incompatibility

[YuukanOO]

For some languages, the definition of extractnumber_xx was incompatible with the use of extract_numbers_generic since it lacks short_scale and ordinals keyword args.

This PR fix this.

It also updates the extractnumber_fr when no number has been found on the given text by returning False instead of a normalized string to make it in sync with all other extractnumber_xx methods in other languages which return a number or False if no number has been parsed. Doing so handle cases such as extractnumbers('2 heures') which failed otherwise.

[devs-mycroft]

Hello, @YuukanOO, thank you for helping with the Mycroft project! We welcome everyone
into the community and greatly appreciate your help as we work to build an AI
for Everyone.

To protect yourself, the project, and users of Mycroft technologies we require
a Contributor Licensing Agreement (CLA) before accepting any code
contribution. This agreement makes it crystal clear that along with your
code you are offering a license to use it within the confines of this project.
You retain ownership of the code, this is just a license.

Please visit https://mycroft.ai/cla to initiate this one-time signing. Thank
you!

[ChanceNCounter]

Properly formatted, fixes an oversight (this fix made it to the Spanish parser, but none of the others.) @YuukanOO even carried the TODO over. What service!

💯

[YuukanOO]

Really like this project and trying to implement the extractduration_fr, I ran into those issues so I fixed them 😉

[ChanceNCounter]

It's occurred to me that these should just return result or False. If you wanna get that change before merging this, cool. If not, we'll deal with it later.

[YuukanOO]

I'll take care of that 👍

[ChanceNCounter]

Thanks! I'll verify this when I'm back at a workstation, if nobody beats me to it.

[ChanceNCounter]

@YuukanOO I thought I commented on this at the time, but I guess I didn't hit submit.

Your authorship got knocked off the commit in a botched attempt to migrate the branch before merging. If I'd realized that would happen, I would just have asked you to check the "contributors can modify" box, but I was clueless and wound up making your name go poof from the repo.

However, there's a major refactor in process that touches these functions again. If it's good by you, I'd like to take the opportunity to put you back in git log, by throwing you in the merge commit message as a collaborator. It'll still be Wrong in git blame, but at least we can put the thing back in your portfolio.

[YuukanOO]

Hi @ChanceNCounter !

Sounds good to me. Stuff like this can happen, not a problem 😉 Thanks for reporting it!