Clean up the MANIFEST
Provide a 'make snapshot'

This is similar to RT's snapshot which makes the dist, signs it and then
shows sha1sums for the person rolling the tarball.
release 3.0.0rc2
search menu tests for 2.9/edit-search-regressions

it's mainly to test "Edit Search" in #page-navigation of pages like Merge,
Link/FromIncident, Link/ToIncident, Incident "Reply to Reporters" and "Reply
to All".
Merge branch '3.0/search-menu-tests' into 3.0.0-releng
Reduce our extra Query Args when pulling from the session.

As discovered by sunnavy when he went spelunking to determine why
t/walk-web.t started running so many extra tests (7a630ac1), we were
stuffing a bunch of extra query params into the query string,
depending on whether we did that from the hash or passed args (things
like Object and Description).

I rewrote his patch a bit to use the same Field list as search_arguments

We lose saved search state badly in RTIR, but it's not a regression
caused by this code, see [rtir #25241]
Better explain the actual behavior of this option.

When introduced in 591dfd0, this option limited the
Transactions/Attachments we were going to FTS on, which makes sense.

For performance reasons, it was removed from the Custom Field searches
prior to 2.4.4 in 8807723.  However, that commit didn't fix the docs,
and it didn't consider that Lookups now act weirdly based on what you're
searching for.

In [rtir #14427] I lay out the history and possible fixes.  For 3.0.0,
documentation is the best solution.
Restore removed simple search by id.

When 7131a78 changed RTIR over to the new Googleish search API, it lost
an important feature.  You could no longer type 7 into the RTIR Simple
Search and jump to 7.  You would be forced into a search for an Incident
with the id of 7, and presented with a results list of 1 (if this was an
incident).  If you were trying to jump to anything but an Incident, you
got an empty search result.

This updates the tests that were written for new features with tests
that ensure this feature works.

Copied core's convention of accepting #1 and 1 so that copy/paste from
email subjects is less confusing.

The confusing Incident search behavior of a list of 1 item also revealed
that RTIR's Search Results do not support core's
$SearchResultsAutoRedirect configuration option.
Merge branch '3.0/simple-search-ticket-redirect' into 3.0.0-releng
Bump version for 3.0.0rc3
Now that 4.0.14 is real, require it.
in case $Query already includes $BaseQuery

here is the old code:

$BaseQuery ||= RT::IR->Query( Queue => $Queue );
$Query     ||= RT::IR->ActiveQuery( Queue => $Queue );

if both $BaseQuery and $Query are empty before, they will be set to
RT::IR->Query(...) and RT::IR->ActiveQuery(...) here, respectively.

but ->ActiveQuery already includes ->Query, so the finaly query will be for
example(combined by BaseQuery AND Query):

( ( Queue = 'Incidents' ) ) AND ( ( Queue = 'Incidents' ) AND Status = 'open' )

so we don't need to set $BaseQuery in this case.

you can reproduce it by accessing "/RTIR/Search/Results.html?Queue=Incidents"
and then clicking the "Edit Search" menu
avoid unnecessary parens when $BaseQuery and $Query are not both set
Add in accidentally skipped files (missed the $ so the .in files were missed)

Also include a new test file.
Merge branch '3.0/search-query-tweak' into 3.0.0-releng
Add in the required ON Transactions clause.
Bump version for 3.0.0rc4
bump version for 3.0.0
Merge branch '3.0.0-releng' into 3.0-trunk
Update drop index command to reference OCFV table