Simpler "use the correct symlink" checks

When determining whether to remove a symlink during unlinking, we check
three things:

  (a) Is the destination a symlink?
  (b) Does the destination exist?
  (c) Does the destination resolve to the source path?

However, since we know that the source path exists, (b) is guaranteed if
(a) and (c) are true. Thus checking (b) is unnecessary.

Similarly, when creating a new symlink during linking, we first check to
see if the link already exists by checking the same three criteria.
Again, checking (b) is unnecessary here.

See also the expanded test coverage in b52b579b.

Addendum: although we know that the source path exists during unlinking,
it doesn't matter. If the source path does not exist, then we still know
we have a broken symlink pointing into the keg we are unlinking, and
removing that symlink is still safe.
Use a regular conditional instead of `next unless ...`
fswatch 1.3.8

Closes #30657.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
fswatch: update 1.3.8 bottle.
czmq: fix checksum for stealth update

Closes #30636.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
libestr 0.1.9

Closes #30640.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
libestr: update 0.1.9 bottle.
python: don't install bottles on Xcode-only systems

Closes #30633.

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
python3: don't install bottles on Xcode-only systems

Signed-off-by: Jack Nagel <jacknagel@gmail.com>
JBoss Forge 2.7.0.Final
jboss-forge: add 2.7.0.Final bottle.