Inconsistent placement props BDropdown and others

[VividLemon]

Clear and concise description of the problem

BDropdown does dropup, dropend, etc. This is quite dumb. A single "location" prop, or position prop should be created instead. Similar, if not the same as, https://vuetifyjs.com/en/api/v-tooltip/#props-location . The goal is to remove these individual position props, and unify them. Then to unify all components to this expected structure

Suggested solution

asdf

Alternative

asdf

Additional context

asdf

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[xvaara]

Should we just use floating-ui ones?

[VividLemon]

What are the differences between the two types?

[VividLemon]

I also need to catalogue what possibly shares "location" values. Location on a drop down popover is different than bcardimg being "end"

[xvaara]

https://floating-ui.com/docs/computePosition#placement

[xvaara]

I kinda would like it to be booleans... Not sure about this but:

// bottom by default. props boolean for left, right and top, and start end.
<BTooltip top end> ... </BTooltip>
<BDropdown left start> ... </BDropdown>
<BPopover start> ... </BPopover>

[VividLemon]

I prefer the simple location prop, as I feel like it's a lot of bloat. Having multiple location items makes the template look weird, and in our code you have to do like 4 or 5 useBooleanish statements. In addition, it also makes it easier to see that these props, top, start, end, etc are all related. I think it would just add a lot more simplicity if they were merged and standard throughout the components.

But speaking of Booleanish, after making the changes to useBooleanish and making it a simple !!, it made me think that allowing strings is kinda silly. We may consider using only booleans instead.