RFC: add assertion utility to test whether a file path resolves to an executable

## Checklist

> Please ensure the following tasks are completed before filing an issue.

- [x] Read and understood the [Code of Conduct][code-of-conduct].
- [x] Searched for existing issues and pull requests.
- [x] If this is a general question, searched the [FAQ][faq] for an existing answer.
- [x] If this is a feature request, the issue name begins with `RFC:`.

## Description

> Description of the issue (or feature request).

This RFC proposes adding an assertion utility to testing whether a file path resolves to an executable. Because of needing to access the filesystem, both an asynchronous and a synchronous API should be provided.

Prior art:

- [isexe](https://github.com/isaacs/isexe): see issues. An implementation may have to contend with edge cases and platform variability.

Package: `@stdlib/assert/is-executable`
Alias: `isExecutable`

## Related Issues

> Does this issue (or feature request) have any related issues?

No.

## Questions

> Any questions for reviewers?

No.

## Other

> Any other information relevant to this issue (or feature request)? This may include screenshots, references, stack traces, sample output, and/or implementation notes.

No.

[code-of-conduct]: https://github.com/stdlib-js/stdlib/blob/develop/CODE_OF_CONDUCT.md

[faq]: https://github.com/stdlib-js/stdlib/blob/develop/FAQ.md