Eco dyno's credits get consumed by unwanted traffic

### Required Terms

- [X] I agree to follow this project's [Code of Conduct](https://github.com/heroku/roadmap/blob/main/CODE_OF_CONDUCT.md)
- [X] I have read and accept the [Salesforce Program Agreement](https://www.salesforce.com/company/program-agreement/)

### What service(s) is this request for?

Eco Dyno

### Tell us about what you're trying to solve. What challenges are you facing?

I currently have an eco dyno for my apps, that are almost used by no one.
Today I saw in the billing pannel that this app has used 381hours of eco dyno in the current month.

Since it was not consistant regarding to what this app is for, I investigated the logs and saw that the app is constantly awoken by unwanted traffic.
By unwanted, I mean essentially robots trying to collect data, or trying to performs attacks.
Here's a non-exhaustive list of calls to the server :

path="/.env"
path="/wp-content"
path="/[www.sql](http://www.sql/)"
path="/robots.txt"
path="/admin/jQuery-File-Upload/server/php/index.php?file=tf2rghf.jpg"
path="/1.sql"

I understand that it is difficult to identify this kind of attacks, but in the end, this makes the "eco dyno" not so eco, since the server is up like 14hours per day for nothing.

I assume it would be great for eco dyno users, and also for you if this kind of requests didn't wake up servers (I can't imagine how many process hours could be saved at the scale the heroku company).

Could it be that such a feature could be implemented ? Or maybe a way for users to specify a white list or black list of paths that are allowed or not to wake up the server ? That would be so great !