Service-catalog: Support displaying and filtering by broker in svcat

[carolynvs]

In cases where more than one broker is installed on a cluster, it would be helpful to display the associated broker in the list of classes/plans, for example:

$ svcat get plans
        NAME                  CLASS                      BROKER                   DESCRIPTION
+------------------+--------------------------+----------------------+----------------------------------------+
  basic              azure-rediscache           osba                    Basic Tier, 250MB Cache
  redis-5-7          redis                      Minibroker              In-cluster installation of Redis 5.7

Additionally, a --broker flag filtering by broker, would be useful:

$ svcat get classes --broker osba
            NAME                      BROKER                         DESCRIPTION
+--------------------------+---------------------------+--------------------------------------+
  azure-rediscache            osba                        Azure Redis Cache
                                                          (Experimental)

[codevulture]

Thanks for the tracker issue, i would also like to work on the change.

[teaguecole]

I didn't notice the previous comment. @codevulture is something you are still actively working on? Any updates?

[carolynvs]

@teaguecole The issue was up for grabs again, so it's all yours. Let me know if you have questions.

[codevulture]

@teaguecole : Caught up in some high priority work so was not able to look in it.

[teaguecole]

This is back up for grabs. Started full time job and school/classes are starting. I will keep my work and if any one wants a good starting point, please let me know as I did good amount of work. You can message me on the #service-catalog channel in Slack.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[nzoueidi]

I am taking this issue, I will start by understand the work done by @teaguecole in the previous closed PRs and I will open one soon.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[mszostok]

/lifecycle frozen

[gmrodgers]

@kubernetes-sigs/service-catalog-maintainers or @mszostok Is it okay if I take this? Looks like there has been no activity on this PR #2643