apheleia-indent-lisp-buffer copies several buffer-local variables to the
scratch buffer before running indent-region, but lisp-indent-offset and
lisp-body-indent are missing. When either of these is set in the
original
buffer, the scratch buffer falls back to different defaults, producing
indentation that disagrees with what indent-region would produce
interactively.

Reproducer: with lisp-indent-offset set to 2, the following form

(setopt
lsp-inlay-hint-enable t
lsp-log-io nil)

formats to one space of indentation instead of two.

Fix: sync lisp-indent-offset and lisp-body-indent from the original
buffer
to the scratch buffer, the same way the existing code already does for
indent-line-function, lisp-indent-function, and indent-tabs-mode.

---------

Co-authored-by: Radon Rosborough <radon@intuitiveexplanations.com>

Seems fairly straightforward to me, Terraform is no longer open-source,
OpenTofu is the compatible open-source successor, similar to the
Redis/Valkey situation.

Of course, if someone still prefers to use Terraform instead, they can
easily customize using:

```tf
(setf (alist-get 'terraform-mode apheleia-mode-alist) 'terraform)
```

We don't have a mechanism for allowing multiple formatters to be
registered for the same major mode, where later ones could be used if
earlier ones are not installed. That might be a nice addition.

Add neocaml-mode and neocaml-interface-mode to the list of modes that
can be formatted with ocamlformat

In OpenBSD and FreeBSD, `diff` don't have support for `--rcs`. In these
cases, we need to use `gdiff` or `GNU diff` for this support.

This change, fix the use of `diff `or `gdiff` for these OSes and make
apheleia work.

The --no-doc argument removes existing document separators (---) from
yaml files. It is perfectly valid and common practice to use multiple
documents within a single file, e.g. in the kubernetes universe.
Formatting such files with --no-doc breaks their validity.

See also the prettier-yaml test, which preserves the document separator,
too.

Behavior of `aphaleia-npx` currently differs from other formatters by
triggering an error when formatter is missing (causing a message to be
displayed in minibuffer and an error buffer to be created).

This PR adds a test to check if command is on user's PATH before
executing it in order to make `aphaleia-npx` silently ends when the
formatter command is not found at project and system level.

## Summary

- Add oxfmt (Oxc Formatter) as a new formatter option for JavaScript and
TypeScript files

## Details

[Oxfmt](https://oxc.rs/docs/guide/usage/formatter) is a Rust-powered,
Prettier-compatible code formatter from the Oxc project. It's currently
in alpha but offers significant performance improvements (30x+ faster
than Prettier).

Key points:
- Uses `inplace` mode since oxfmt doesn't support stdin/stdout
- Works with all common JS/TS extensions (.js, .jsx, .mjs, .cjs, .ts,
.tsx, .mts)
- Not added to `apheleia-mode-alist` - users can opt-in by setting
`apheleia-formatter` to `oxfmt`
- Defaults are already sensible: 2-space indent, printWidth 100, no tabs

Example usage:
```elisp
(setf (alist-get 'oxfmt apheleia-formatters)
      '("apheleia-npx" "oxfmt" inplace))

;; To use for JS/TS files:
(setq-default apheleia-formatter 'oxfmt)
;; Or per-mode:
(setf (alist-get 'typescript-ts-mode apheleia-mode-alist) 'oxfmt)
```

This make rubocop obey exclusions from config files. Otherwise, even if
a file is excluded from in .rubocop.yml, apheleia will still format it.

See
https://docs.rubocop.org/rubocop/usage/basic_usage.html#command-line-flags