Idea: determine `entry_points` automatically from `*.dist-info/entry_points.txt` for `noarch: python` packages

### Checklist

- [x] I added a descriptive title
- [x] I searched open requests and couldn't find a duplicate

### What is the idea?

Currently `noarch: python` recipes (both v0 and v1) require including a list of `entry_points:` manually. However, the respective packages already carry the upstream list of entry points in the `*.dist-info/entry_points.txt` file.

The idea (as initially discussed with @jaimergp) would be to change the `entry_points` for `noarch: python` packages to allow three kinds of values:
- an explicit list of entry points (the current behavior)
- `true` to automatically discover entry points from `entry_points.txt`
- `false` to disable automatic discovery and not create any entry points

### Why is this needed?

The current behavior of having to manually "copy" `entry_points` is both cumbersome and carries a potential of missync if people miss changing entry points upstream.

### What should happen?

_No response_

### Additional Context

I may be missing something non-obvious as to why this wouldn't work.