Load WMS with the "ignore extent" option

[FilipLeitner]

Description

• allow loading of WMS layers from composition with ignoreExtent predefined. Can be tested using this composition
• buffer default extent for WMS layers added via URL or Catalogue to 'make space' for clipped symbology.

Related issues or pull requests

closes #4863

Pull request type

Please check the type of change your PR introduces:

• [x] Bugfix
• [x] Feature
• [ ] Dependency updates
• [ ] Code style update (formatting, renaming)
• [x] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] Documentation content changes
• [ ] Other (please describe)
• [ ] I am unsure (we'll look into it together)

Do you introduce a breaking change?

• [ ] Yes
• [x] No
• [ ] I am unsure (no worries, we'll find out)

Checklist

• [x] I understand and agree that the changes in this PR will be licensed under the [MIT License]
• [ ] I have followed the guidelines for contributing
• [ ] The proposed change fits to the content of the code of conduct
• [ ] I have added or updated tests and documentation, and the test suite passes (run npm test locally)
• [ ] I'm lost; why do I have to check so many boxes? Please help!

[FilipLeitner]

First part of #4863 is a bit problematic and yet to be solved. Layer extent set in layer constructor gets overriden by extent parsed from metadata

• made some changes how extent is parsed for WMS layers constructed in add-data ( Catalogue and URL) and prevented duplicated extent parsing in layermanager while keeping the functionality there for composition layers. There is still a bit of redundancy as both getSingleLayerExtent of add-data and getCapsExtent of layermanager do mostly the same.

Second part is basically ready but theres some problem with visiblity toggle as layer is missing when I tested resulting in throw that is not handled (95a968d)

[FilipLeitner]

Not sure, what is the *.db-journal file, but I guess it shall not be pushed in git and rather .gitignored, right?

17c5b1e