Add behavior flags to jinja context

[mikealfare]

Problem

BaseAdapters.behavior is a dynamic property (uses @property). We use @available to make methods available in the jinja context, but this mechanism relies on the method being callable. Using the @property decorator first supplies @available with something that is not callable. Using the @available decorator first adds _is_available_ to the value of the property, but the property object that @property returns does not have the _is_available_ attribute.

Solution

Subclass property and hard code _is_available_ = True on it.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development, and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.