Machine Coding: Build a Smart Task Scheduler with Cooldown

Problem Statement

In a high-intensity coding environment, "Context Switching" is the biggest productivity killer. You are tasked with building a Task Priority Scheduler that mimics a smart VS Code extension. The scheduler must manage tasks based on their urgency and estimatedTime, but it must also implement a "Cool Down" period to prevent developer burnout.

Implement a class TaskScheduler with the following requirements:

1. addTask(task): Adds a task object { id, urgency, estimatedTime } to the queue.
2. getNextTask(): Returns the task with the highest urgency. If two tasks have the same urgency, return the one with the shortest estimatedTime (Shortest Job First).
3. completeTask(id): Marks a task as completed. After a task is completed, no new task can be started for a "Cool Down" period of 10ms per estimatedTime unit of the completed task.
4. isAvailable(): Returns true if the developer is not in a cool-down period, false otherwise.

Example

const scheduler = new TaskScheduler();
scheduler.addTask({ id: 1, urgency: 5, estimatedTime: 100 });
scheduler.addTask({ id: 2, urgency: 5, estimatedTime: 50 });

console.log(scheduler.getNextTask().id); // 2 (Same urgency, shorter time)
scheduler.completeTask(2); 

console.log(scheduler.isAvailable()); // false (In 500ms cool down)
// After 500ms...
console.log(scheduler.isAvailable()); // true

Constraints

• 0 <= urgency <= 10
• estimatedTime is in milliseconds.
• The scheduler should handle up to 1000 tasks.