Export bug_tracker APIs for upstream components

[Bryce Harrington]

The Launchpad API should provide routines to make it easy to access information about a bug watch.

Some rough brainstorming (subject to change extensively):

  * getProductsForBugtracker - List of products supported by a given bugtracker
  * getComponentsForProduct - List of components for a given product in a remote bugtracker
  * getRemoteProduct(remote_bug) - Given a remote bug id that exists in launchpad, identify its product
  * getComponentForSourcePackage - Identify the remote bug tracker component that corresponds to a source package

  * setComponentForSourcePackage - allows programmatic linking of component and source package
  * setSourcePackageForComponent - allows programmatic linking of component and source package

Perhaps others...

This bug is a work-item for the following LEP: https://dev.launchpad.net/LEP/BugzillaComponents

[Bryce Harrington (bryce)]

Several of these just fell out of the basic implementation of the model/interface stuff, so I'll just need to doublecheck that they're getting exported properly and can be accessed from scripts.

  * getProductsForBugtracker - Available as BugTracker:component_groups
  * getComponentsForProduct - Available as BugTrackerComponentGroup:components
  * getRemoteProduct(remote_bug) - see below
  * getComponentForSourcePackage - will be solved by bug #644794

  * setComponentForSourcePackage - will be solved by bug #644794
  * setSourcePackageForComponent - will be solved by bug #644794

getRemoteProduct() might not be needed. For existing bug watches, they *should* already have the product included with the watch. For upstream bugs not associated with a bug watch, I think we don't care about providing a lookup function there. So I don't think we need anything done for this routine.

[Launchpad QA Bot (lpqabot)]

Fixed in db-stable r9908 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-stable/revision/9908>.