fix: Use logging instead of print during materialization

[Shizoqua]

Summary

This PR removes direct print() usage from Feast’s materialization flow and replaces it with standard library logging. This avoids writing to stdout from library code while still surfacing materialization progress and warnings via configured log handlers.

Changes

• Replace print() calls in FeatureStore.materialize, materialize_incremental, and ODFV materialization helper logic with logger.info/logger.warning.
• Remove unused colorama import (Fore, Style) after eliminating colored stdout output.

Testing

• python -m compileall sdk/python/feast/feature_store.py

[Shizoqua]

@franciscojavierarceo Good day
What am I to do next?

[Shizoqua]

@franciscojavierarceo

Good day, my PR was approved 2 days ago but I haven't had any response since then.

[ntkathole]

@Shizoqua There are unit tests failing for this change. Also, I think this changes the default cli console output for feast materialize or materialize-incremental commands. Since default cli logging configured as warning, there is no console output for these commands after this change.

[Shizoqua]

Hi @ntkathole ! thanks for the catch.
I have updated it as requested.

[franciscojavierarceo]

@ntkathole that's true it does change the default output. That's probably the right thing actually. We need to make sure we set

import logging
# This sets the root logger level to INFO
logging.basicConfig(level=logging.INFO)

@Shizoqua can you ensure this?

This is actually probably much better as we can add logging.debug more intentionally in the code. At the moment we dump a lot of info.

[Shizoqua]

This is actually probably much better as we can add logging.debug more intentionally in the code. At the moment we dump a lot of info.

I will start working on it now