Reducing number of tasks for connector causes deleted tasks to show as UNASSIGNED

If a connector is successfully created with t1 running tasks and then reconfigured to use t1 - n tasks (where t1 and n are both whole numbers and n is strictly less than t1), the connector should then list t1 - n total tasks in its status (which can be queried via the /connectors/:name:/status endpoint or the /connectors endpoint with the expand URL query parameter set to status).

However, the connector will instead continue to list t1 total tasks in its status, with n of them being listed as UNASSIGNED and the remaining t1 - n of them being listed as STARTED.

This is because the only time a task status is removed from the status backing store (as opposed to simply being updated to UNASSIGNED) is when its connector is deleted. See relevant code snippets from the AbstractHerder and DistributedHerder classes.