Add is_enterprise_install flag for org wide installation support

[hussachai]

Introducing the inclusion of the 'is_enterprise_install' parameter in commands, interactions, and oauth2 responses. This flag is essential for facilitating organization-wide installations within the enterprise grid environment. Without this flag, the authentication token mapping process becomes unreliable, as it necessitates attempts with both the enterprise ID and team ID, potentially resulting in unexpected outcomes.

Pull Request Guidelines

These are recommendations for pull requests.
They are strictly guidelines to help manage expectations.

PR preparation

Run make pr-prep from the root of the repository to run formatting, linting and tests.

Should this be an issue instead

• is it a convenience method? (no new functionality, streamlines some use case)
• exposes a previously private type, const, method, etc.
• is it application specific (caching, retry logic, rate limiting, etc)
• is it performance related.

API changes

Since API changes have to be maintained they undergo a more detailed review and are more likely to require changes.

• no tests, if you're adding to the API include at least a single test of the happy case.
• If you can accomplish your goal without changing the API, then do so.
• dependency changes. updates are okay. adding/removing need justification.

Examples of API changes that do not meet guidelines:

• in library cache for users. caches are use case specific.
• Convenience methods for Sending Messages, update, post, ephemeral, etc. consider opening an issue instead.

[parsley42]

LGTM

[parsley42]

@lololozhkin Any objections? Care to add a review?

[parsley42]

Sorry slow to get this in; appears to be more complete than #1255