feat: add version field to ExecutionContext

[Weijun-H]

Which issue does this PR close?

Closes #1517

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

[alamb]

Thanks @Weijun-H

I realize #1517 says "ExecutionContext" but this code is in the experimental "scheduler"

I wonder if #1517 meant to say SessionContext or SessionState or TaskContext (or perhaps the code has been changed since the ticket was filed)

[alamb]

What do you think about adding a function like

pub fn version(&self) -> &str {
...
}

Which would avoid the need for allow(dead_code) perhaps

[Weijun-H]

Thanks @Weijun-H

I realize #1517 says "ExecutionContext" but this code is in the experimental "scheduler"

I wonder if #1517 meant to say SessionContext or SessionState or TaskContext (or perhaps the code has been changed since the ticket was filed)

I vote for SessionState, because it is the execution context for executing queries. What do you think? 🤔

[alamb]

Thanks @Weijun-H !

[alamb]

I think you could just call env!("CARGO_PKG_VERSION") here -- is there any reason to create a string to do so?

Suggested change

	&self.version
	env!("CARGO_PKG_VERSION")

[alamb]

Thank you @Weijun-H 👍