Replaced config.groovy with config.jelly in GlobalQuietPeriodConfiguration

[StefanSpieker]

Replaced config.groovy with config.jelly in GlobalQuietPeriodConfiguration

Testing done

Ran Jenkins in debug mode and verified that saving and loading works, and also verified that the localization still works:

Proposed changelog entries

• N/A

Proposed changelog category

/label internal

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.
• 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.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• 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).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

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

Maintainer checklist

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• 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).
• 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).

[MarkEWaite]

Thanks!

[daniel-beck]

Removes existing form validation by removing clazz:"number" without justification.

Before

After

via

jenkins/war/src/main/webapp/scripts/hudson-behavior.js

Lines 1288 to 1292 in 23f2b9e

	Behaviour.specify("INPUT.number", "input-number", ++p, function (e) {
	e.addEventListener("keypress", preventInputEe);
	registerMinMaxValidator(e);
	registerRegexpValidator(e, /^((-?\d+)|)$/, "Not an integer");
	});

[StefanSpieker]

Removes existing form validation by removing clazz:"number" without justification.

Before

## After

via

jenkins/war/src/main/webapp/scripts/hudson-behavior.js

Lines 1288 to 1292 in 23f2b9e

	Behaviour.specify("INPUT.number", "input-number", ++p, function (e) {
	e.addEventListener("keypress", preventInputEe);
	registerMinMaxValidator(e);
	registerRegexpValidator(e, /^((-?\d+)|)$/, "Not an integer");
	});

Thanks @daniel-beck
I wasn't aware that this is handled by the clazz. Seems to work:

Thinking about adding this to the developer documentation, do we have a list of which general validations there are?

[janfaracik]

Thinking about adding this to the developer documentation, do we have a list of which general validations there are?

Unsure if there is such a page, there is a very general/old one in https://weekly.ci.jenkins.io/design-library/validation/ that could be adapted?