The default 404 handler would return the Content-Type format based on the
given format extension. This would cause the Rails CSRF protection to flag an
error, since the .js extension gets mapped to text/javascript format.

Closes #40771

Otherwise we'd only preload the ancestors that would fit the
page. That way, when a search result was on the first page, but the
ancestor didn't fit the page anymore. We would not have the preloaded
ancestor when rendering the hierarchy.

When a project is shared with a group, it should not be included as a
descendant on the group dashboard.

When searching we would limit the scope of ancestors to load because
the filter would be applied to the ancestors. Instead, we need to load
_all_ ancestors for matching projects.

Html code now works in commits atom feed `title` and `summary`.

Given no search term, the `search` and `search_with_secondary_emails` methods will yield an empty result set

Without this, it's very hard to locate it.

Put back non triggered information