Clarify a few points of documentation. Fixes #1475.

[ci skip]
Use dep-key for distinct call in pom task.

group/artifact version tuple isn't enough to de-dupe correctly.

Fixes #1494.
Emit success message after install.

Normally I prefer to remain silent if everything succeeds, but the
fact that install calls pom and jar, which are not silent, means it's
confusing if you don't see anything for install itself.
Actually use :plugin-repositories. Fixes #1474.
Fix weird de-duping behaviour in pom.

It used to be we would merge a bunch of profiles into the project, and
then trim out dupes based on group/artifact/version, which was totally
wrong; it ignores classifiers and extensions.
Normalize :aot :all to :aot [:all].

This fixes type mismatch issues when merging profiles.

Fixes #1488.
Remove mention of :omit-default-repositories.

Fixes #1472.
Check for key not found message from gpg 2.x as well.

Fixes #1462.
Prevent NPE when pedantic encounters dupe top-level deps to fix #1498
Merge pull request #1504 from jcrossley3/1498

Prevent NPE when pedantic encounters dupe top-level deps to fix #1498
PROFILES.md - be really explicit about overriding

While "Declaring Profiles" states that "Profiles specified in `profiles.clj` will override
profiles in `project.clj`," some less attentive reader can interpret it so that *keys/values* from profiles.clj override those from project.clj, not that the profile as whole is replaced. This changes
tries to make it really clear. (Of course feel free to change the wording as you see fit.)
Update PROFILES.md
Merge pull request #1506 from jakubholynet/patch-1

PROFILES.md - be really explicit about overriding
Merge :plugin-repositories into :repositories before loading plugins.
Catch exceptions updating indices in lein search. Fixes #1508.
Catch and print query parsing exceptions in search task. Fixes #1507.
PROFILES.md: Tip to use composite profile

Sometimes we need to override *parts* of a prticular profile on a project-specific base. To a novice
lein user, it is likely not clear how to achieve this. This tip points her in the right direction -
using a composite profile with a "personal" part that can be overriden in `profiles.clj` to change
what is in the "common" part of the profile.
Add structure of the newly created sample template

I think it might be better to provide a quick look at the new template structure before going to any detail?
Merge pull request #1509 from jakubholynet/patch-2

PROFILES.md: Tip to use composite profile
Check user profile's plugin-repositories when looking for templates.

Fixes #1510.