text: Title: [FEA] refactor pygraphistry[ai] logger to be more pythonic & friendly
  Body: The pygraphistry[ai] files (feature_utils, umap, ..) are doing some surprising & awkward use of `logging` that make dev + usage difficult, it should probably be:
  
  - [ ] files initializes as `logger = setup_logger(__filename__)`, drop parameter `verbose`, and drop use of static config file
  - [ ] maybe add level `TRACE` as deeper than current `DEBUG`:
      - TRACE: include data outputs (df values, ...)
      - DEBUG: verbose but limit data outputs (just df shapes, ...)
      - INFO: just occasional status
      - WARN/ERROR/CRITICAL: as usual
  - [ ] use env var `GRAPHISTRY_LOG_LEVEL` if available 
  - [ ] enable library to easily dynamically toggle: 
      - `logging.getLogger('graphistry').set_level(logging.DEBUG)`
      - `logging.getLogger('graphistry.some_file').set_level(logging.DEBUG)`
      - maybe a convenience getter, `graphistry.logger`