### Description of Changes
Tag operations in UI would not be rendered properly when using the paginated tags endpoint.
When a user would create/delete a tag from the repo-panel-tags, `digest` would be called. This caused the `$scope.repository.tags` to be removed.
To fix this:
* Bind the tags directly to the scope instead of the repository
* Change references to scope.repository.tags to use scope.repositoryTags
---
* endpoint/api/repository: limit the number of tags returned
- Limit the number of tags returned by /api/v1/repository/<ns:repo> to 500.
- Uses the tag history endpoint instead, with an active tag filte.
- Update UI to use tag history endpoint instead.
The user metadata fields are nullable in the database, but were not in
the json sechema. This prevented users from updating some of their
information on the site if they hadn't set the metadata fields.
We no longer allow viewing individual images, but instead only manifests. This will help with the transition to Clair V3 (which is manifest based) and, eventually, the the new data model (which will also be manifest based)
includes the options for maximum search results per page, and the
maximum number of pages available before help text is shown, and
the next page button is disabled
before we were setting the location on the window when we should have been just using Angular $location service instead
[TESTING -> tested locally with docker compose and a complete build]
- [ ] It works!
- [ ] Comments provide sufficient explanations for the next contributor
- [ ] Tests cover changes and corner cases
- [ ] Follows Quay syntax patterns and format
* starting UtilService refactor
* pre find-replace angular.module('quay') => angular.module('QuayModule')
* successfully switched to ng-metadata for backported Angular2 API
* working with parent component reference in child
* fixing @Output to use EventEmitter
* fixed @Output events for custom git trigger
* more fixes
* refactored QuayPages module for backwards-compatibility
* reinitialized test.db
* use minified libraries
* replaced references for angular-ts-decorators
* fixed ng-show
Take ownership code got moved into its own directive in Oct, but we forgot we have a call in superuser panel for orgs as well. Fix this, and simplify the call sites
Adds warnings displayed in the superuser config tool that the changes made will only be applied to the local instance (in non-k8s case) or that a deployment is required (in the k8s case)
[Delivers #137537413]
