Assume new classes won't have Visual Recognition API keys

[dalelane]

cf. https://cloud.ibm.com/docs/visual-recognition?topic=visual-recognition-release-notes#1december2020

From 7th Jan 2021, it won't be possible to create new Visual Recognition API keys.

I want to allow existing classes to continue to use their existing API keys, while not asking new classes to.

[dalelane]

https://github.com/IBM/taxinomitis/blob/5eecc4d4b898ffcb1c6e60293a26e916005637f3/src/lib/db/objects.ts#L1085

Default classes should not include images as a project type any more

[dalelane]

https://github.com/IBM/taxinomitis/blob/5eecc4d4b898ffcb1c6e60293a26e916005637f3/ops/tenant.sh#L6

Newly created classes should not include images as a project type any more

[dalelane]

Hundreds of classes are using the current default class definition and have paid Visual Recognition API keys.

select distinct classid from bluemixcredentials where credstypeid=4 AND classid NOT IN (select id from tenants);

They will need new tenant definitions stored that matches the current default, before the default is changed, to allow them to continue using their API keys.

[dalelane]

The docs that explain how to set up API keys should be updated, too.

https://github.com/IBM/taxinomitis-docs/blob/master/docs/msword/machinelearningforkids-apikeys.key