### What is the current behavior?
Fixes Submitty
[Issue#11784](Submitty/Submitty#11784) - This
one of the companion PRs to Submitty
[PR#12609](Submitty/Submitty#12609).

### What is the new behavior?
submitty_count is longer installed in preparation for deprecation.

### Other information?
<!-- Is this a breaking change? -->
This is a breaking change. Any autograding that uses the old
submitty_count instead of submitty_count_ts will no longer work.
<!-- How did you test -->
1. Follow the instructions on [this
page](https://submitty.org/instructor/autograding/docker_images) up to
step 6 with the Dockerfile modified in this PR. (you may be able to
reuse the one I used `dagemcn/dockerimages:default-test` adding it
through docker UI)
2. After you have added the new docker image with the DockerUI, update
the config of any gradeable with `submitty_count` with
```
"autograding_method": "docker",
"container_options": {
    "container_image": "IMAGE_NAME"
},
``` 
where `IMAGE_NAME` is the name of the image, for example,
`dagemcn/dockerimages:default-test` if you reused mine.
3. Create a gradeable using submitty_count, (Tutorial examples 04, 06,
and 07 all utilize submitty_count)
4. Test that submitty_count will not work in the config and that
submitty_count_ts successfully runs
5. Also test that regular autograding works successfully on the image

Attached is a zip of a sample solution and gradeable config with both
submitty_count and submitty_count_ts commands present for testing.

[example.zip](https://github.com/user-attachments/files/29638384/example.zip)

### What is the current behavior?
Fixes Submitty
[Issue#11784](Submitty/Submitty#11784) - This
one of the companion PRs to Submitty
[PR#12609](Submitty/Submitty#12609).

### What is the new behavior?
submitty_count is longer installed in preparation for deprecation.

### Other information?
<!-- Is this a breaking change? -->
This is a breaking change. Any autograding that uses the old
submitty_count instead of submitty_count_ts will no longer work.
<!-- How did you test -->
1. Follow the instructions on [this
page](https://submitty.org/instructor/autograding/docker_images) up to
step 6 with the Dockerfile modified in this PR. (you may be able to
reuse the one I used `dagemcn/dockerimages:csci1200-test` adding it
through docker UI)
2. After you have added the new docker image with the DockerUI, update
the config of any gradeable with `submitty_count` with
```
"autograding_method": "docker",
"container_options": {
    "container_image": "IMAGE_NAME"
},
``` 
where `IMAGE_NAME` is the name of the image, for example,
`dagemcn/dockerimages:csci1200-test` if you reused mine.
3. Create a gradeable using submitty_count, (Tutorial examples 04, 06,
and 07 all utilize submitty_count)
4. Test that submitty_count will not work in the config and that
submitty_count_ts successfully runs
5. Also test that regular autograding works successfully on the image

Attached is a zip of a sample solution and gradeable config with both
submitty_count and submitty_count_ts commands present for testing.

[example.zip](https://github.com/user-attachments/files/29638384/example.zip)

### What is the current behavior?
Fixes Submitty
[Issue#11784](Submitty/Submitty#11784) - This
one of the companion PRs to Submitty
[PR#12609](Submitty/Submitty#12609).
The tutorial courses 04 - Python Static Analysis, 06 - Loop Types, and
07 - Loop Depth all use `submitty_count` in their autograding configs.
This command is being deprecated, so we should update it.

### What is the new behavior?
`submitty_count` has been removed from `04 - Python Static Analysis` and
`06 - Loop Types` and replaced with `submitty_count_ts` in preparation
for deprecation. For `07 - Loop Depth`, there was no equivalent
functionality present in `submitty_count_ts` so the testcase is entirely
commented out.

### Other information?
<!-- Is this a breaking change? -->
This specific PR is not a breaking change. However, the other PRs
accompanying this one are breaking PRs.
<!-- How did you test -->
Tested that all homework configs still build and their accompanying
still submissions work as intended.