Implement query with interpolation flags

[ozgurcancal]

Summary

Add support for explicit interpolation flags to specify exactly which interpolation features should be enabled in the query.
Add integration tests for possible flag combinations.
Update README.

Reference: #157

[pravic]

It's better to use the log crate here.

Suggested change

	eprintln!(
	"warning use QI::BIND template flag,bind() skipped for query: {}",
	self
	);
	log::warn!("use QI::BIND template flag,bind() skipped for query: {self}");

[ozgurcancal]

Thanks, This is the default macro stated in the macros.rs

[pravic]

Changing a public type should be a major version bump.

Can this be avoided, by the way? What is the purpose of having INTERPFLAGS here instead of a regular setter?

[ozgurcancal]

Thanks for your comment. I think discouraging unconscious use of bind or fields function should be query wise. Otherwise, it would appear less intuitive and introduce unnecessary complexity, since these functions are commonly used with both execute and fetch.
Therefore, handling interpolation only in fetch would not be sufficient. If fetch were the only place where interpolation was needed, I would simply enable all flags (including bind and fields) and update the interpolation state directly via the fetch function template argument.

[ozgurcancal]

I have fix the conflicts in the PR, we can implement the raw query on the top of it. what do you think? @slvrtrn @loyd