Remove self package reference in ui-components

[james-wills-sf]

While exploring creating a npm package fork, I ran into an issue where I couldn't change the @bloom-housing org name in package.json because there was an @bloom-housing/ui-components import from within ui-components.

This seems like a mistake, so this change switches it to a local import instead. This might be something we can lint for?

[jaredcwhite]

Absolutely. Not sure what we'd use to lint this but happy to get something like that set up. Was it just this once instance, or are there other cases lurking about?

[james-wills-sf]

@jaredcwhite I could only find the one instance. It looks like there are @bloom-housing/ui-components in ui-components/.storybook but when I changed those to relative imports storybook failed to run. I don't really know much about how storybook gets its assets and they don't break anything so I'm fine with keeping those imports as-is.

[james-wills-sf]

Looked into linting this, you could use something like import-blacklist but that would require some refactoring since you'd need linting rules specific to each package directory.

Not necessary for now, maybe something to think about if it comes up again

[james-wills-sf]

@jaredcwhite looks like tests are passing. I'll leave it to you to do the merge since idk bloom's merge and deploy processes

[jaredcwhite]

LGTM!