InterpolationException silently swallowed in AbstractEarModule.getBundleFileName()

## Description

In `AbstractEarModule.java:268-271`, an `InterpolationException` from `MappingUtils.evaluateFileNameMapping()` is silently swallowed:

```java
} catch (InterpolationException e) {
// We currently ignore this here
// FIXME: should we handle this better?
}
```

If the file name mapping evaluation fails, the exception is completely ignored. The `bundleFileName` field remains `null`, and downstream code using `getUri()` (which calls `getBundleFileName()`) may get unexpected null values. The FIXME comment confirms this is a known issue.

## Expected behavior

At minimum, log a warning:

```java
} catch (InterpolationException e) {
getLog().warn("Failed to evaluate file name mapping", e);
}
```

Open AbstractEarModule.java at lines 268-271 and trace getBundleFileName() through getUri(); inspect how MappingUtils.evaluateFileNameMapping() failures and nearby logging are handled. Run the relevant existing tests, then verify that an InterpolationException is no longer silently ignored and that downstream callers do not receive an unexpected null without a warning.

Written by the indexing model from the issue text.