Sort package by trust level and filter out packages from ports (ARM, PowerPC)

[guoyunhe]

Ordered by trust level (official packages first)

Search result will be ordered by trust level:

• 3: official package (user's choice)
• 2: official package in Factory
• 1: experimental package
• 0: community package

For package with the same level, package with shorter name will be shown first.

Before (MozillaFirefox is at 5th):

After (MozillaFirefox is at 1st):

Initial baseproject and other search settings

For fresh installed system (without cookies), the search settings modal popup and let users choose their system.

Filter out packages different from architecture of users' chosen baseproject

For normal distributions, filter out ARM and PowerPC

Settings saved in cookies instead of URL

Settings in modal will be stored in cookies and send with every request. The advantage of using cookies is:

• Share link safely. If we share a link on wiki or forum with baseproject parameter, clicking it will modify users' cookies. However, others' settings are probably not for you. So URL parameter should only contains something common for users to share, like q=Firefox is common, but baseproject=openSUSE:Leap:42.1 from an old article is not.
• On the same machine, people don't change baseproject, search_devel etc. that much.
• It becomes possible to ask user for their choice of baseproject when not set.

[guoyunhe]

build symbols, language packages, devel packages should have lowest priority. they are not filtered out by user settings, which causes many unwanted results.

[guoyunhe]

Now language, buildsymbols, devel package can be filtered out.

[guoyunhe]

Detect User-Agent of HTTP request, we can filter out packages that doesn't match users' system architecture. On x86_64 system, none of ARM, PowerPC, zSystems packages show.

Compare wireshark page:

Before

After

[guoyunhe]

Fix #301 #299 #137

[agraul]

This does not seem to work properly for me, this happened when I searched for Firefox:

It is an improvement, but the user still has to know which to pick.

For the removal of showing packages that have a different arch, I don't like that the user has no control over that. Le't say you have a RPi and want to search for available software from your PC, this does not work if ARM results are filtered out by User-Agent. There should be a way to have them displayed.
I also wonder if querying OBS for all the packages and then throwing them away is the best approach.

On a different note, I think we should not put all this the controller. I'd say we should have a package model with this kind of logic (priority etc), but that is out of scope for this PR.

[guoyunhe]

For fresh installed system (without cookies), the search settings modal popup and let users choose their system.

[dmacvicar]

I am looking at this one locally. I get a failed test, which I am trying to fix.

[dmacvicar]

I thought the test needed to be adapted but the problem is that the modal buttons are not working, so that the settings dialog does not get closed.

[guoyunhe]

If you click on ok button, it will save cookies and refresh page. If you click cancel button, settings will be reset and modal will be closed.

[dmacvicar]

I understand. I am trying to find why I can't get the tests to run locally, even if they are passing on Travis. I also locally don't get the modal to work correctly.

[dmacvicar]

Got it. I am refactoring trust_level and adding a test before merging.