Bump i18n-js to latest prerelease

User Story # 15318

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Correct configuration for i18n-js w/asset pipeline

`I18n::JS::Middleware` is only necessary if we're not using the Rails
asset pipeline.

See https://github.com/fnando/i18n-js#rails-app-with-asset-pipeline

If we migrate away from the asset pipeline, this commit should be
reverted.

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Remove erroneously committed translations file

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Remove redundant I18nJsHelper

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Lay out wp attributes using CSS flexible boxes

This implementation stops long attribute values from "breaking" the
layout.

Bug # 14596

Signed-off-by: Alex Coles <alex@alexbcoles.com>
API v2 PE index: Allow disabling parent rewiring

Allow disabling rewiring - this exposes parent IDs of work packages invisible
to the user.
When requesting single work packages via IDs, the rewiring fails as it assumes
that all visible work packages are loaded, which they might not be. For a work
package with a parent visible to the user, but not included in the requested IDs,
the parent_id would thus be nil.
Disabling rewiring allows fetching work packages with their parent_ids
even when the parents are not included in the list of requested work packages.

There's also a case when rewiring is not used at all: When not providing a project
id and requesting via /api/v2/planning_elements.json?ids=[...]. In this case
parent_ids were and are always shown. This is pretty inconsistent, but that's
the way API v2 is. Btw, planning_elements.json returns 404 when not giving an ids
parameter.

Apparently, the way custom fields are returned is also different between
the general planning elements endpoint and the project-specific one. I didn't
look into this, though.
shows correct casing for custom_field names on wp#show
correctly concatenates params when flags are present
fix german translation in en locale
Merge pull request #1893 from opf/fix/german_translation_in_en

fix german translation in en locale
uses fully qualified route on users memberships

This avoids problems when other controllers render the partial
Merge pull request #1892 from opf/fix/filters_on_export_with_descriptions

correctly concatenates params when flags are present
moves category out of the first two rows of the detail pane
Do not allow wp attribute values to wrap

Bug # 14596

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Use explicit classes for attribute labels, values

* Do not use <label> outside of an HTML form context.

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Add small right padding to wp attributes

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Revert "make filter operator select focusable and keep track in query filters di..."
Merge pull request #1895 from opf/fix/category_at_correct_place

moves category out of the first two rows of the detail pane
fix gravatars have no alt attribute in details pane
Merge pull request #1894 from opf/fix/use_full_qualified_route_on_users_memberships

uses fully qualified route on users memberships