Refine content and appearance of the project 'Configure' screen

[janfaracik]

This pull request updates the content and minor styling of the project 'Configure' screen to provide descriptions for each section, fix the sidebar for Pipeline projects, and decrease section padding a little. This is part of an ongoing effort to simplify Jenkins' many forms.

Changes

• Sections now have descriptions to explain what they're for
• Some section titles have been tweaked, dropping the 'Build' prefix. These are: 'Build Triggers' -> 'Triggers', 'Build Environment' -> 'Environment'. This has been done to help differentiate their labels at a glance.
• Section description margins have been decreased
• Pipeline sections now show in the sidebar

Before

After

Testing done

• Form works as before

Proposed changelog entries

• Refine content and appearance of the project 'Configure' screen

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@jenkinsci/sig-ux

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[janfaracik]

/label web-ui,rfe

/reviewer @jenkinsci/sig-ux

[janfaracik]

Please add trailing periods to full sentences. Otherwise it'll be inconsistent or plain weird once a section has more than one sentence

Done :)

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[timja]

LGTM - could you file a corresponding PR to pipeline please for consistency?