Fix Taxonomy tests.

@Grevil: That's funny, perhaps taxonomy_term is the one we need to use?

See core/modules/taxonomy/src/Entity:

/**
 * Defines the taxonomy term entity.
 *
 * @ContentEntityType(
 *   id = "taxonomy_term",

vs.

/**
* Defines the taxonomy vocabulary entity.
*
* @ConfigEntityType(
* id = "taxonomy_vocabulary",

Yeah use: taxonomy_term

Ugly naming history...

@Grevil does this still happen? If yes and it's simple to fix, please fix it. If not, leave it open for later, but I think we should then rate this as bug.

Yea, still no idea, how to properly do this. So "taxonomy_term" is the entity type name? What is the "bundle" name then? The bundle of the created term?? I have no idea...

Setting "taxonomy_term" as entity type and "$term->bundle()" as the bundle, leads to the error message:

InvalidArgumentException: Field field_access is unknown.

Setting both entity type and bundle to "taxonomy_term" OR setting entity type to "taxonomy_term" and bundle to "$vocabulary->bundle()" will lead to:

LogicException: Missing bundle entity, entity type taxonomy_vocabulary, entity id taxonomy_term.

Let's postpone this for now.

Setting "taxonomy_term" as entity type and "$term->bundle()"

is the correct one, I think.

The bundle is for example "tags" here at taxonomy terms, I guess.

InvalidArgumentException: Field field_access is unknown.

might be correct, perhaps the field isn't added correctly...

In contrast to all other entity types, the Config Entity (vocabulary) has a different name here from the Content Entity ("taxonomy_term") while for other entity types it's just node_type => node, ...

But yes, not important enough so far.

@Anybody, makes sense! Let's fix this in the future!