v0.2.0

Added

• Applications left without a key are listed under the inventory, with what they still allow:
  revoking a key leaves its application behind, and an application is a key and a secret a new
  credential can be requested under.
• Deletion of an application that holds no key, behind a confirmation. An application still
  holding one is never offered, because OVHcloud revokes every key of an application along with
  it; the count is checked against the API at the moment of the deletion.
• Deletion of every application holding no key in one pass, behind a confirmation listing them.
  The request carries no list: the set is selected on the server from what the API answers, and
  the report says which applications were deleted and which were refused.
• The management key can hold GET /me/api/application and DELETE /me/api/application/*,
  which the listing and the deletion need. Both are optional, like the credential delete rule:
  without them the section says which rule is missing, and a key issued before this version
  keeps working.
• An Understand screen, in English and French, explaining what an application, a key and an
  access rule each are, on an invented example, and what follows from the way they fit
  together. It reads nothing from the account.

Changed

• The quick start gives the ready-made management key link for each of the three endpoints
  instead of ovh-eu alone, so an account on ovh-ca or ovh-us no longer has to rebuild the
  address by hand. A test ties those links to the rules the code asks for.